Posted: Sun Jan 07, 2018 19:19 Post subject: Linksys E3000
Router/Version: Linksys E3000
Firmware: DD-WRT v3.0-r34311 mega (12/29/17)
Kernel: Linux 3.10.108 #17154 Fri Dec 29 10:44:11 CET 2017 mips
Previous: DD-WRT v3.0-r34080 mega
Mode/Status: AP / gateway
Reset: No
Issues/Errors: Wireless clients fail to load (or delayed) internet pages very often.
Speedtest: 20/200Mb (=max)
edit:
see issues
Last edited by jopiexjoker on Tue Jan 23, 2018 19:03; edited 1 time in total
You could also enable "Query DNS in strict order" (although if all all added DNS servers fail it will use your ISP DNS server)
I had assumed the behavior change with /tmp/resolv.dnsmasq was related to the recent security upgrades but unfortunately am limited to cocaine-snorting comcast(US) for internet.
A tick box to include/exclude ISP DNS servers for Auto-DHCP WAN seems to be the correct mechanism.
You could also enable "Query DNS in strict order" (although if all all added DNS servers fail it will use your ISP DNS server)
I had assumed the behavior change with /tmp/resolv.dnsmasq was related to the recent security upgrades but unfortunately am limited to cocaine-snorting comcast(US) for internet.
A tick box to include/exclude ISP DNS servers for Auto-DHCP WAN seems to be the correct mechanism.
Cheers,
Unfortunately the no-resolv+server=x.y.z did not work, ISP DNS is still placed in /tmp/resolv.dnsmasq regardless of what is in Static server(s). I'll stick with my workaround for now
Edit: Simpler than I originally thought:
Code:
# workaround to remove ISP DNS for Auto-DHCP WAN:
[ "`nvram get wan_get_dns`" != "" ] &&
nvram unset wan_get_dns &&
nvram unset wan_get_domain &&
nvram commit &&
stopservice dnsmasq &&
startservice dnsmasq
Need an automatic mechanism ala inotify to handle async events, eg, lease renewals.
Mode/Status: Gateway/Access Point (wired/wireless)
Issues/Errors: Completely unresponsive (no pings to gateway address) after about 24 hours. Received WPA2 "wrong password" message on iOS after router became unresponsive. Required power-cycle to start working again.
2.4GHz AP: OK, but received "wrong password" message on iOS after router became unresponsive.
5GHz AP: OK, but received "wrong password" message on iOS after router became unresponsive.
I could no longer stand the amount of connection problems with iOS and wrong password errors on my R8500 so I reverted to stock firmware.
I really don't understand how such a fundamental issue has not been addressed in the months I have been using DD-WRT.
While stock is not as flexible as DD-WRT, and there is an issue with radio stability with smart connect enabled (so I have it off), the overall signal strength seems better and my iOS devices no longer lose connections.
By the way, I found that simply hitting Apply on the wireless security tab was enough to allow them to connect, did not need to restart the router. Although in your case it seems like a little more drastic failure if it becomes entirely unresponsive.
Mode/Status: Gateway/Access Point (wired/wireless)
Issues/Errors: Completely unresponsive (no pings to gateway address) after about 24 hours. Received WPA2 "wrong password" message on iOS after router became unresponsive. Required power-cycle to start working again.
2.4GHz AP: OK, but received "wrong password" message on iOS after router became unresponsive.
5GHz AP: OK, but received "wrong password" message on iOS after router became unresponsive.
I could no longer stand the amount of connection problems with iOS and wrong password errors on my R8500 so I reverted to stock firmware.
I really don't understand how such a fundamental issue has not been addressed in the months I have been using DD-WRT.
While stock is not as flexible as DD-WRT, and there is an issue with radio stability with smart connect enabled (so I have it off), the overall signal strength seems better and my iOS devices no longer lose connections.
By the way, I found that simply hitting Apply on the wireless security tab was enough to allow them to connect, did not need to restart the router. Although in your case it seems like a little more drastic failure if it becomes entirely unresponsive.
I have the same experience with my R7000 router and Android or whatever WiFi device.
It almost is a casino, when will the WiFi or WAN connectivity brake?! It just isn't stable.
I also had problems with wireless on android devices using my Linksys e900 router with DHCP Disabled.
No errors, they would show as connected in the gui but internet won't work on them and pinging them would return destination host unreachable.
Another weird issue was with Netflix, with no downloads in the background the subtitles would get out of sync or stop showing after 10 minutes or so, having to stop and start again the video to fix it.
Also the WAN speed is pretty low when downloading torrents and stuff. It would stay more than a minute at 4-5MB/s then really slow going up to 7-7.5MB/s and stay there. TCP Congestion Control Vegas 4096, 1024, 120, QOS disabled..
Now I'm back to v3.0-r33555 mega (10/20/17) Netflix is working fine, wireless is stable, WAN download goes to 8MB/s in less than 20 seconds and soon after hits 9.5 - 10MB/s and stay there.
This is using the same exact settings, same everything.
Joined: 22 Aug 2009 Posts: 267 Location: New York State
Posted: Tue Jan 23, 2018 18:05 Post subject: Re: ASUS RT-AC68U & Linksys E2000
Newbrain wrote:
Asus RT-AC68U
Firmware: DD-WRT v3.0-r34311 std (12/29/17) - (previous r34080)
CPU Temperature: CPU 79.1 °C / WL0 52.0 °C / WL1 51.4 °C
Note: After adding a fan to the box (it is in a small closed compartment) the temperature dropped significantly:
CPU 64.1 °C / WL0 44.2 °C / WL1 44.4 °C
Posted: Wed Jan 24, 2018 8:21 Post subject: Re: ASUS RT-AC68U & Linksys E2000
videobruce wrote:
Newbrain wrote:
Asus RT-AC68U
Firmware: DD-WRT v3.0-r34311 std (12/29/17) - (previous r34080)
CPU Temperature: CPU 79.1 °C / WL0 52.0 °C / WL1 51.4 °C
Note: After adding a fan to the box (it is in a small closed compartment) the temperature dropped significantly:
CPU 64.1 °C / WL0 44.2 °C / WL1 44.4 °C
174 F, ouch, what was it with previous builds?
80C is completely fine, even 90. So the fan was useless. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
Not in mt book by a long shot. I bet you overclock your processors too. Electronics runs hot enought, why push it past the excessive limit as it is
Kind suggestion. Buy a new book man, or google it. This isn't x86. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
Posted: Fri Mar 16, 2018 22:58 Post subject: Firewall command script not working on reboot
Here is my router info:
Router Model:Asus RT-AC68U B1
Firmware: DD-WRT v3.0-r34311 std (12/29/17)
Kernel:Linux 4.4.108 #2419 SMP Thu Dec 28 18:49:56 CET 2017 armv7l
Everything looks good, but having a minor issue that the router is not running the firewall script
