I have Dnsmasq v2.57 running on a router (Tomato USB), where it gets invoked as 'dnsmasq -c 1500 --log-async' and uses a config like (edited):
interface=br0 resolv-file=/etc/resolv.dnsmasq addn-hosts=/etc/dnsmasq/hosts dhcp-hostsfile=/etc/dnsmasq/dhcp expand-hosts min-port=4096 stop-dns-rebind rebind-localhost-ok dhcp-range=192.168.1.100,192.168.1.149,255.255.255.0,10080m dhcp-option=3,192.168.1.1 dhcp-lease-max=255 dhcp-authoritative # persistent lease file dhcp-leasefile=/mnt/ext_flash/var/run/dhcp-leases # static DHCP hosts dhcp-host=00:14:d1:f1:c7:e6,cctv1,192.168.1.225,infinite The router gets rebooted daily, and I'm trying to get the "static" lease to persist across reboots. Here's what I'm seeing: 1. Router restarts. 2. cctv1 reboots, requests a lease, and is added to lease file. 3. cctv1 is pingable by name. 4. Router is rebooted. 5. Initially cctv1 still exists in lease file. 6. A ping of cctv1 fails with a bad host name, and has disappeared from the lease file. The expectation is that in step 6 the cctv1 client should still be pingable. What caused it to disappear from the lease file? Also, I don't understand how the 'dhcp-authoritative' directive (quoting the man page) "allows dnsmasq to rebuild its lease database without each client needing to reacquire a lease, if the database is lost." I'm not sure how that could work. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/
