Well, good news for me, it's not only "affecting" my device 
(Joke mode ON)
Maybe other LEDE users can show us their result.
here ya go!
global
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
es
global
country ES: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
pa
global
country PA: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5735 - 5835 @ 80), (N/A, 30), (N/A)phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
nz
country NZ: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
Here are my results, both radios are set to ES.
global
country ES: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
so what about this, you think this is what i need to do with the patches?
http://wiki.openwrt.org/doc/devel/patches#refreshing_patches
I'm sorry, but I'm confused about where and what do FW vs download, if possible can you give me a quick orientation? I intend to return my DD-WRT C7 to the LED and to work it with a WRT1900
I appreciate the help
what i believe you should do is revert back to stock firmware
then i would follow the guide on lede for how to flash openwrt/lede to your device.
https://openwrt.org/playground/qsg_lede_installation_guide
hope that helps, again make sure you know which version you have of archer c7
also check this topic
@sycohexor Thanks for reply,
and I'm sorry, I did not make myself well understood, my WRT1900 is already running the LEDE, I need to install it back in my Archer C7, this with the DD-WRT but I went back to the STOCK Fw ja, now I'm in doubt which vs LEDE install, since there is a root and a new one, then I wanted to see which one is more current and stable.
my idea to put the WRT1900 and Archer C7 together in my home network.
no that was my mistake, i didnt read that properly, but im not to sure about which build is better tbh...you could always just try one for a week and then try another for week and see what happens. i edited the above post, sorry bout that.
1 Like
@cliobrando, have you experienced any problems with 5 ghz and client association with your build? could the krack patch be causing this? i dont think i had it on before when i was using @r00t nightlys.
nope, no problem here.
so i was having problems with out of range with anything over channel 50 in 5 ghz ,my google home and anything amazon and roku devices, once i changed it, that resolved the issue. i dont know if its just those particular devices or what my issue is. my apple devices worked fine on any channel. but pretty good build so far, i dont use the recursive dns cuz i forward it to pihole and pihole now has quad 9 with dnssec. it has a dhcp server as well. along with ipv6 support. what do you set your breed to? i have it at 25 so 1000 mhz, oh and this isnt just related to your build, ive tried it on @r00ts too, same issue.
Friends, I would like to indicate which version is running better on Archer C7v2, because from what I understand there is another variant of the one made by @root.
so if anyone can quickly update me on this new vs, what are the differences, benefits etc .... I am grateful because I want to leave the router to use with the standardized FW.
I already thank you for the help, and please send the download link and if you need any different procedures to be used.
thankful
https://www.gargoyle-router.com/ coming to a lede near you!
Experimental: 1.9
https://www.gargoyle-router.com/downloads/images/ar71xx/gargoyle_1.9.2-ar71xx-generic-archer-c7-v2-squashfs-factory.bin
Nothing special with the Gargoyle Router Fork. It was released last year. 
Beware of the warning: WARNING 1: Current firmware (1.9.0 and earlier) has been reported to brick recent models of Archer C7 v2 (Early 2016 and later)
It worked for me when I played a few days with it.
Go with the original FW - if you miss something you can try a Community Build.
I'd rather use gargoyle than some of the crap I've seen produced here.
Stick with ddwrt man. Only thing good that came from this forum was the
breed bootloader.
Pretty confusing comment, what do you think Gargoyle is based on?
Figure it out.
hey if you guys use bcp38 with hue devices and connect to their servers, here is a way to control it via debug api, i had issues with bcp38 constantly disconnecting the bridge from the servers because it acquires your local ip address, in order to link with the bridge.
Hej everybody, first off: thanks @root for your efforts! it enabled me to actually build my own firmware! good job with the optimisations!
Unfortunately, I ended up locking myself out of my device and I am therefore unable to even connect to it or make any changes to the settings. I tried to enter filesafe mode but I am unable to. I tried every thing I could find online and before I get out my usb2serial adapter: can anyone confirm that failsafe does not work with this build? If it does with your device: when did you push that pesky button? Thanks!
Hi @sycohexor,
I have never used Gargoyle, but in your opinion, what makes Gargoyle better than LEDE/OpenWRT? It has any fuction that we can't find in LEDE (HW NAT, better WiFi....)?
Thanks @sycohexor