Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Sat Jun 01, 2019 21:45 Post subject:
Mile-Lile wrote:
SinCalChewy wrote:
kernel-panic69 wrote:
SinCalChewy wrote:
Router/Version: 2x Linksys E3000
Firmware: dd-wrt.v24-39884_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-39866_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #24659 Thu May 30 15:10:10 CEST 2019 mips
Mode: Both basic client bridges with everything not required turned off.
Status: Working, however see below
I've used these two E3000 boxes for a long time now with no problem. But sometime in the last few builds (I don't know exactly what one, apologies), when setting the DHCP server to off, as well as dnsmasq to off (both not required for a client bridge), upon reboot, the dnsmasq toggle is enabled and there is a dnsmasq process running with "/tmp/dnsmasq.conf" as the file (which I never set up...). It caused a few issues, which I solved with this in the startup script:
Code:
# Disable dnsmasq as it seems to be starting on boot <-- Unwanted!
nvram set dnsmasq_enable=0
rm /tmp/dnsmasq.conf
killall dnsmasq
After adding that, the computers/devices get correct assignments from the AP router really quick. Before adding that, it was a hit or miss with how fast they got their assigned IP (normally took awhile).
I figured this out as I was doing a total rebuild of all my networks, so I think it's not supposed to happen? And if it is, mind informing me why and what it does? Like I said, I got much better performance when disabling and killing the "rouge" dnsmasq server on my client bridges.
Good day.
Did you set all dnsmasq related settings to disabled on services tab and un-check all dhcp-related settings on basic setup tab? There's some sort of magic voodoo to make it work, usually, but then again, the 'fix' to remove udhcpd was 'incomplete'... perhaps.
I spent a good two or so hours trying to disable it via the GUI. I disabled everything dhcp and dnsmasq, and still, every reboot dnsmasq would "re-enable" itself. For now the "fix" I posted works (speeds much faster), but I will definitely be checking into doing it in a less "hack-y" way.
you can disable DHCP from basic setup page... just set it to disable... you cannot disable whole dnsmasq because it is used for DNS... e.g. ntpclient uses DNS if you enter hostanme as a time server...
For sure, thank you for the info! I will work with that then. _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
Joined: 18 Mar 2014 Posts: 12908 Location: Netherlands
Posted: Sun Jun 02, 2019 15:39 Post subject:
In general YES.
Some explanation
Resetting before was/is necessary to make room for the upgrade, in the old days with little flash ram it could be that there was insufficient room and that the upgrade could become stuck, I have once bricked a router when I had JFFS2 enabled and did not reset before update.
That said on all my modern routers I do not reset before upgrading (I am no fan of JFSS2 but that is another story)
The most important reset is after upgrading, the best way is to telnet to your router and do:
Code:
nvram erase && reboot
but some routers do not like this command and could brick, so research if this is applicable otherwise reset with the reset button or from the GUI.
Of course put settings in manually do not resotre from a backup otherwise you introduce the same "garbage"
Do I always reset after upgrading to a new build?
No not always, if it is an incremental upgrade I do not reset.
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Tue Jun 04, 2019 13:21 Post subject: DD-WRT BS build 39884 and Asus RT-N18U
Router/Version:Asus RT-N18U(rev. A1)
Firmware: DD-WRT v3.0-r39884 std (05/30/19)
Kernel: Linux 4.4.180 #140 PREEMPT Thu May 30 09:07:38 CEST 2019 armv7l
Previous: DD-WRT v3.0-r39800 std (05/15/19)
Mode: WAN @ DHCP, Wireless @ AP
Status: Working (not 24/7 & not using IPv6, VAP, VPN, NAS nor USB)
Reset: NO reset during firmware upgrade but cold boot
Problems:
1. /var/log/messages had no entry, file size was zero. I had remote logging enabled.