Couldn't get DNS to resolve. First indication was because it couldn't get a time, which has happened to be before with DNSSEC enabled - confirmed that it was not enable. Hunted around in the DNSMASQ log and saw that every query was being returned (DNS was not resolving). Scrolled up and saw that it said "no upstream servers configured".
At that point I double checked the main Setup page and confirmed that I did indeed have DNS servers listed. I tried disabling strict order in case it was an error with one server - no resolution.
I then specified each server in the additional config options on the Services page and all is now working.
I did not do a reset after flashing this build (R8000) and I'm not really wanting to do that at this point. So no clue if it is an NVrAM artifact or not.
Quit working overnight, couldn’t get any DNS to resolve. Reset via web GUI, prompted to reset password but then I can’t access anything else in the Web GUI. Did another reset (hardware button since I could t get into GUI) and it still isn’t working. So now I’m at a loss. Will have to work it some more when I get home. Since I can’t get into the GUI nor SSH in, this will be interesting.
Max Power wrote:
Couldn't get DNS to resolve. First indication was because it couldn't get a time, which has happened to be before with DNSSEC enabled - confirmed that it was not enable. Hunted around in the DNSMASQ log and saw that every query was being returned (DNS was not resolving). Scrolled up and saw that it said "no upstream servers configured".
At that point I double checked the main Setup page and confirmed that I did indeed have DNS servers listed. I tried disabling strict order in case it was an error with one server - no resolution.
I then specified each server in the additional config options on the Services page and all is now working.
I did not do a reset after flashing this build (R8000) and I'm not really wanting to do that at this point. So no clue if it is an NVrAM artifact or not.
Got it working. Something is preventing DNS queries when I add the code below to the DNSMASQ additional config field. These options worked previously. With the options added the router cannot resolve time.nist.gov which prevents all other internet access. In the logs for DNSMASQ it says that no upstream servers are configured with the options listed below. No clue why anything I have in the additional config would cause that error.
Quit working overnight, couldn’t get any DNS to resolve. Reset via web GUI, prompted to reset password but then I can’t access anything else in the Web GUI. Did another reset (hardware button since I could t get into GUI) and it still isn’t working. So now I’m at a loss. Will have to work it some more when I get home. Since I can’t get into the GUI nor SSH in, this will be interesting.
Max Power wrote:
Couldn't get DNS to resolve. First indication was because it couldn't get a time, which has happened to be before with DNSSEC enabled - confirmed that it was not enable. Hunted around in the DNSMASQ log and saw that every query was being returned (DNS was not resolving). Scrolled up and saw that it said "no upstream servers configured".
At that point I double checked the main Setup page and confirmed that I did indeed have DNS servers listed. I tried disabling strict order in case it was an error with one server - no resolution.
I then specified each server in the additional config options on the Services page and all is now working.
I did not do a reset after flashing this build (R8000) and I'm not really wanting to do that at this point. So no clue if it is an NVrAM artifact or not.
-R, --no-resolv
Don't read /etc/resolv.conf. Get upstream servers only from the command line or the dnsmasq configuration file.
I wonder how it worked in the previous configuration?
I use "no-resolv" as well and specify the DNS servers by the "server=" statement in the additional dnsmasq config section.
As far as I know: In the file /etc/resolv.conf you find the IP adresses of the DNS servers defined by the GUI on the setup page and/or the DNS server IP received from WAN interface via dhcp. But I'm not sure about the correct behavior, therefor I use the "no-resolv" parameter and specify my dns server explicitly.
Joined: 08 Jun 2010 Posts: 109 Location: New Zealand
Posted: Thu Oct 04, 2018 19:20 Post subject:
Router: Asus RT-AC3200
Firmware: DD-WRT v3.0-r37015M kongac (09/23/1
Kernel: Linux 4.4.157 #603 SMP Sun Sep 23 01:10:11 CEST 2018 armv7l
Previous Firmware: DD-WRT v3.0-r36840M kongac (09/03/18 )
Mode/Status: Gateway / AP / IPsec
Upgrade Method: "ddup --flash-latest". No 'erase nvram'
Reset: Power Cycle after ddup
Uptime: 45 minutes
Errors: None so far
CPU Temp 63.6 °C
This looks like it is running about 4 or 5 degrees hotter than r36840 where I was getting around CPU 59.5 °C
This also seems hotter than what other devices on here are running at? Should I be concerned?
What is the expected temp on an RT-AC3200?
EDIT: 36 hours of uptime and CPU 66.9 °C - This seems to be running hotter than before.
Posted: Wed Oct 10, 2018 14:23 Post subject: I confirm "running hotter" on R7000 as well.
spaceghost wrote:
Router: Asus RT-AC3200
Firmware: DD-WRT v3.0-r37015M kongac (09/23/1
Kernel: Linux 4.4.157 #603 SMP Sun Sep 23 01:10:11 CEST 2018 armv7l
Previous Firmware: DD-WRT v3.0-r36840M kongac (09/03/18 )
CPU Temp 63.6 °C
This looks like it is running about 4 or 5 degrees hotter than r36840 where I was getting around CPU 59.5 °C
This also seems hotter than what other devices on here are running at? Should I be concerned?
What is the expected temp on an RT-AC3200?
EDIT: 36 hours of uptime and CPU 66.9 °C - This seems to be running hotter than before.
Yep. My "office" Netgear R7000, running as an AP with dual 2.4/5.0 wireless and a couple of wired clients, runs at CPU temp 64 - 65 C on this version.
My "older" machines (identical) have
Firmware Version
DD-WRT v3.0-r31205M kongac (02/03/17)
at only 55 °C, and a couple of "Client Bridge" systems running at even colder temps (51 °C) using
DD-WRT v3.0-r34900M kongac (02/11/1.
Joined: 16 Nov 2015 Posts: 6440 Location: UK, London, just across the river..
Posted: Thu Oct 11, 2018 5:35 Post subject:
on my R7000 addn-hosts=/tmp/ its not created
my adblocker doesn't work as intended
there is something with DNSmasq
it was fin on the older builds
or its a fake line in syslog... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Routers: Netgear R6700 v3 and Netgear R6400 v1
Firmware: DD-WRT v3.0-r37015M kongac (09/23/18
Kernel: Linux 4.4.157 #603 SMP Sun Sep 23 01:10:11 CEST 2018 armv7l
Previous Firmware: DD-WRT v3.0-r36840M kongac (09/03/18 )
Mode/Status: Gateway / AP
Upgrade Method: "ddup --flash-latest". Had to finally 'erase nvram' to get it to work on both routers.
Reset: Power Cycle after ddup
Uptime: 2 days
Errors: Yes
CPU Temp 63.6 °C (R6700v3) & CPU 60.2 °C (R6400v1)
Sorry if I'm late to the party, but I finally got them working.
Tried to update the R6400v1 first since I use it as a repeater bridge to the R6700v3. Bridging would not work with encryption until both routers were updated. Maybe its a clue that it looks like the menu names for encryption types changed from the previous release.
As others have seen, VAPs die after awhile. I use one for guest access. Interestingly, if I have a device that automatically reconnects, such as my cell phone, then the VAP will stay active. Once I turn off auto-reconnect, then the VAP dies within about 15 minutes.
Routers: Netgear R7000
Firmware: DD-WRT v3.0-r37015M kongac (09/23/1
Kernel: Linux 4.4.157 #603 SMP Sun Sep 23 01:10:11 CEST 2018 armv7l
Previous Firmware: Forgot
Mode/Status: Gateway / AP
Upgrade Method: "ddup --flash-latest". with'erase nvram' before and after upgrade
Reset: no
Uptime: 23 days, 1 min
Errors: No
From what I've seen. This has been a solid build so far. I'm about to upgrade to the new ver.
Posted: Sun Dec 02, 2018 16:43 Post subject: Static DNS Broke?
Router NameDD-WRT
Router ModelNetgear R7000
Firmware Version DD-WRT v3.0-r37015M (09/23/1
Kernel VersionLinux 4.4.157 #603 SMP Sun Sep 23 01:10:11 CEST 2018 armv7l
Loaded this version last night. Factory reset. Loadeddd-wrt.v24-K3_AC_ARM_STD.bin with defaults checked. Manually added all of my configurations (did not restore from a previous versions backup).
Worked fine, until this morning when I decided to add static DNS entries. As soon as I add any DNS entry all WAN traffic stops. I can not ping 8.8.8.8 from any host on the network. Only syslog messages that seemed relevant were NTP failures to an IP I had previously configured. I looked at incoming and outgoing logs to see if any traffic was being dropped/passed. No reports on either one, which confirms no traffic was passing the WAN. I tried removing the DNS entry, and still no traffic over the WAN. I had to initiate another factory reset, and reconfigure my PPPoE to restore connectivity. Anybody else see this issue? I'm still poking at it to see if I can figure it out. Any direction is appreciated.
