DHCP server issues with .48 beta 3 anyone?

[Zonkd]

Recently upgraded my RT-AC68U from 376.47 (20-Sept-2014) to 376.48 Beta 3 (02-Nov-2014). I manually put back all my settings - rather than restoring from a config backup - to avoid any issues.

I'm now finding that DHCP server will not renew a clients IP address lease once it has expired. For me this happens after a day, so I need to reboot the router every time a client is disconnected. I realize I can just extend the expiration time, or go to each client and manually configure it with an IP address, but I wanted to see if anyone else has this issue?

Oh and Airplay seems to randomly crash since upgrading to these more recent firmwares. I realize many readers won't be using Apple devices / airplay, but has anyone else had this issue?

 

[L&LD]

After flashing the new firmware, did you do a factory reset?

 

[Zonkd]

Thanks for the response!

Yes I did. Factory reset -> Flashed -> Factory reset -> Manually reconfigured with previous settings.

At one point I tried requesting the renewal of DHCP lease from my client. Didn't work. I checked the router log and I think it said something like "no leases remaining".

Is nobody else experiencing this? All the clients on my network keep losing their IP. For now I've tried extending the lease time to a week.

 

[L&LD]

Did you setup a new SSID with no special characters and / or forget the original SSID on each client and re-associate again with the router?

I would also suggest leaving as many settings to default with new firmware and slowly change and test the settings a single setting at a time to be sure that any tweaks you made previously still need to be used.

 

[ColinTaylor]

I checked the router log and I think it said something like "no leases remaining".

"something like..." Well if you've got an actual error message it would be helpful to know what is said exactly.

Look in your router's log for a message similar to this:

dnsmasq-dhcp[9341]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d

What does yours say?

 

[JGrana]

I had a similar issue crop up using more recent .48 firmware's (RT-87R). Don't recall which beta, but I found that some devices would show connecting over the WiFi but not connect.

For some background, I have ~20 pre-defined static IP address to MAC address under DHCP, starting at 192.168.1.50. I then allow a small range of addresses for DHCP to provide (like 192.168.1.10 to 192.168.1.30). So a mixed bag, but not overlapping.

On looking at the logs, I had "no leases left" messages from dnsmasq. I looked at dnsmasq.conf and discovered that dhcp-lease-max was set to 21!!! I suspect the new software that generates the dnsmasq.conf file counts fixed addresses (like my 20) and uses that as the dhcp-lease-max. Must be new.

For now, I have solved the issue by creating a dnsmasq.postconf file in /jffs/scripts with this code:

#!/bin/sh
CONFIG=$1
source /usr/sbin/helper.sh
pc_replace "dhcp-lease-max=21" "dhcp-lease-max=100" $CONFIG

Now, dnsmasq.conf has a dhcp-lease-max of 100 and all is running fine now.

Hope this helps your case.

 

[RMerlin]

After a whole month of beta this just comes out the evening I upload 376.48? /me hits his head on the keyboard.

For now you can indeed fix it using a postconf script. I'll see about pushing out an update.

 

[RMerlin]

It's yet another bug that was introduced by Asus in 376_2769. Sigh. I'll do what they used to do before that, and hardcode that value to 253, hoping that they will have a proper fix in 376_3602, which should be available next week.

 

[RMerlin]

Thanks for tracking it down JGrana. I've replaced the 2769 complicated max-lease calculation with a hardcoded value of 253 like Asus were previously doing. I've rebuilt and reuploaded all six firmwares as 376.48_1. I revert that code back once Asus fixes it on their end.

 

[JGrana]

Your very welcome - sorry it came out so late!

More important, thank you for applying a quick fix and getting it into the release.

Cheers

 

[nyxagamemnon]

Lol I guess this explains why my modem would randomly loose connection everyday at a certain time. I revered to .47 and it went away but LOL

 

[ColinTaylor]

Lol I guess this explains why my modem would randomly loose connection everyday at a certain time. I revered to .47 and it went away but LOL

Not really. They're two different things.

 

[Zonkd]

Thanks for fixing this so promptly Merlin!