Funny...update -03 brought with it local name resolution issues
Without details, I'll take a crack at what he might be seeing. Local name resolution does in some cases make use of the dnsmasq.leases file. When you reboot or load code it gets wiped out since it's kept in ram.
Now, the wireless clients see the drop and request new leases. The wired clients, however, do not....and wait for their local lease time to expire before requesting a new lease. And if they are not configured with a fixed ip address, the router doesn't know about them by name. Until they request a new lease, local name resolution for wired clients without a fixed ip won't work. In order for them to get a new lease, you would need to unplug/plug the ethernet cables for each one.
The solution....move the leases file to non-volatile store so it survives reboots. I keep mine in a /jffs/tmp directory. Two things need to be done.
First....add the appropriate lines to
dnsmasq.postconf script.
Code:
#!/bin/sh
CONFIG=$1
source /usr/sbin/helper.sh
pc_insert "resolv-file=/tmp/resolv.conf" "dhcp-leasefile=/jffs/tmp/dnsmasq.leases" $CONFIG
Second, the webui is hardwired to look in the default location, so make a symlink to the new leases file in the
init-start script.
Code:
#!/bin/sh
# Symlink to non-volatile dhcp lease file
ln -s /jffs/tmp/dnsmasq.leases /tmp/var/lib/misc/dnsmasq.leases
Now you can either let the new lease file populate itself, or 'seed' it with your existing file by copying /tmp/var/lib/misc/dnsmasq.leases to your new location. Reboot and you are done.
After this there won't be any delay in local name resolution. Note that this is really only for routers up 24/7 to be accurate. It you power down the router for long periods, it won't hurt anything, but the leases data of course won't be correct.