Your reports for Broadcom units are greatly appreciated !
Router:
Firmware:
Kernel:
Previous:
Status:
Reset:
Errors:
This build thread is for reporting successes and problem with loading this experimental test build. This is important info for developers and users. Always state your hardware and SPECIFIC build (e.g. 30796_NEWD-2_K2.6_mega-nv64k.bin). Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved. Please also do not respond to such questions. This thread is to report info, not to seek it. Posts that do not add to understanding this build will be deleted. Make sure you know how to flash properly and the risk before using this build. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless.
If you don't know what build to flash and how to flash properly and have a means of recovery if things should go wrong, do NOT flash this experimental test build.
Last edited by Xeon2k8 on Wed Nov 16, 2016 13:55; edited 1 time in total
Router: Asus RT-AC56U
Firmware: DD-WRT v3.0-r30880M kongac (11/14/16)
Kernel: Linux 4.4.32-rc1 #144 SMP Mon Nov 14 23:08:29 CET 2016 armv7l
Previous: 30870
Status: OK
Reset: NO
Errors: NONE
Router: Netgear R8000
Firmware:DD-WRT v3.0-r30880M kongac (11/14/16)
Kernel: Linux 4.4.32-rc1 #144 SMP Mon Nov 14 23:08:29 CET 2016 armv7l
Previous: 30870
Status: OK
Reset: NO
Errors: DNSSEC is working upon enabling "Recursive DNS Resolving" setting, however after any reboot, WAN loses connectivity and it is only recovered if that setting is disabled. So, in case of any power outage, there is no Internet, if DNSSEC enabled, after power is restored.
Posted: Wed Nov 16, 2016 3:37 Post subject: Re: R8000
-XPTO- wrote:
Router: Netgear R8000
Firmware:DD-WRT v3.0-r30880M kongac (11/14/16)
Kernel: Linux 4.4.32-rc1 #144 SMP Mon Nov 14 23:08:29 CET 2016 armv7l
Previous: 30870
Status: OK
Reset: NO
Errors: DNSSEC is working upon enabling "Recursive DNS Resolving" setting, however after any reboot, WAN loses connectivity and it is only recovered if that setting is disabled. So, in case of any power outage, there is no Internet, if DNSSEC enabled, after power is restored.
I thought DNSSEC also needs a dns resolver that supports DNSSEC (dnscrypt resolver mostly)?
Did you set a dnscryp server as dns server/resolver?
Joined: 13 Mar 2014 Posts: 856 Location: Montreal, QC
Posted: Wed Nov 16, 2016 6:16 Post subject: Re: R8000
ciscodlink wrote:
-XPTO- wrote:
Router: Netgear R8000
Firmware:DD-WRT v3.0-r30880M kongac (11/14/16)
Kernel: Linux 4.4.32-rc1 #144 SMP Mon Nov 14 23:08:29 CET 2016 armv7l
Previous: 30870
Status: OK
Reset: NO
Errors: DNSSEC is working upon enabling "Recursive DNS Resolving" setting, however after any reboot, WAN loses connectivity and it is only recovered if that setting is disabled. So, in case of any power outage, there is no Internet, if DNSSEC enabled, after power is restored.
I thought DNSSEC also needs a dns resolver that supports DNSSEC (dnscrypt resolver mostly)?
Did you set a dnscryp server as dns server/resolver?
dnscrypt has no direct connection with DNSSEC as all that dnscrypt does is encrypt the connection between the router and dns resolver. DNSSEC is entirely dependent on the resolver. ex. you can use dnscrypt with opendns but opendns does not support dnssec so it will fail dnssec tests.
wheras you can run your own dns resolver such as unbound, bind9, etc and have full dnssec protection and obviously have no need for dnscrypt. you can also just use google's public dns servers with no dnscrypt support and have full dnssec protection as dnssec is built in.
**edit
forgot dnsmasq is now compiled with dnssec support, just make sure the nameservers you choose supports dnssec and enable in dnsmasq and your done
root@R7000:~# ddup --flash-latest
wget: bad address 'www.desipro.de'
Was DNS or your internet down?
Oh yes, sorry, it was a DNS error, I resetted NVRAM and forgot the local DNS empty to 0.0.0.0.0 (the R7000 is a secondary router behind the main R7800) Thanks.
Just updated my R7000 to r30880M kongac (11/14/16). All seems ok but it has just few minutes of uptime and it's only an access point/switcher, so no heavy work on it!
There is def a problem that has crept into the builds. The 5GHZ band is missing channels from 100-144. I tried multiple regulatory domains including Russia and no joy.
As a possible hint, those channels must use DFS and maybe that's why they are gone. The DFS is not required for the Russia regulatory area.
I rolled back to 8/24/16 30432 build which I had on my PC and the channels are back.
The missing channels are not shown in the web gui and they can't be selected with the wl commands.
Posted: Wed Nov 16, 2016 13:28 Post subject: Re: R8000
JAMESMTL wrote:
ciscodlink wrote:
-XPTO- wrote:
Router: Netgear R8000
Firmware:DD-WRT v3.0-r30880M kongac (11/14/16)
Kernel: Linux 4.4.32-rc1 #144 SMP Mon Nov 14 23:08:29 CET 2016 armv7l
Previous: 30870
Status: OK
Reset: NO
Errors: DNSSEC is working upon enabling "Recursive DNS Resolving" setting, however after any reboot, WAN loses connectivity and it is only recovered if that setting is disabled. So, in case of any power outage, there is no Internet, if DNSSEC enabled, after power is restored.
I thought DNSSEC also needs a dns resolver that supports DNSSEC (dnscrypt resolver mostly)?
Did you set a dnscryp server as dns server/resolver?
dnscrypt has no direct connection with DNSSEC as all that dnscrypt does is encrypt the connection between the router and dns resolver. DNSSEC is entirely dependent on the resolver. ex. you can use dnscrypt with opendns but opendns does not support dnssec so it will fail dnssec tests.
wheras you can run your own dns resolver such as unbound, bind9, etc and have full dnssec protection and obviously have no need for dnscrypt. you can also just use google's public dns servers with no dnscrypt support and have full dnssec protection as dnssec is built in.
**edit
forgot dnsmasq is now compiled with dnssec support, just make sure the nameservers you choose supports dnssec and enable in dnsmasq and your done
Thank you, so choose a dns resolver that supports dnssec and enable the "recursive dns resolving".
Any devices that are using dnscrypt+dnssec already on the device itself are not affect by the dns-resolver that the router uses? So ln my latop I use dnscrypt with dnssec, that means what ever dns-resolver I set in dd-wrt, my laptop will continue to use dnscrypt where as devices without any explicit set dns-server will use what the router is set up to?