Check your log, see if the camera is reporting a wrong MAC, different client-id, different vendor class, or something like that.
Or possibly the camera's bootloader is remembering its old address (gotten before you configured your hosts file) and requesting a renewal. Again, the log would show a renewal request. On Tue, Dec 20, 2011 at 10:21 AM, Claes Parflo <claes.par...@gmail.com> wrote: > Hello, > > I allocate IPs from hosts file. All goes well for D-Link IP cams, > but TRENDnet IP cams get random DHCP IPs instead of MAC address bound > addresses. This is resolved only by entering respective cam and issuing > reboot. After reboot the correct IP is received, not via power-off/on. > > I have emptied /var/lib/misc/dnsmasq.leases before adding cam's and > sent SIGHUP before powering on cam's. > > Allocated IPs by dnsmasq after cold boot: > root@debian:/# cat /var/lib/misc/dnsmasq.leases > 1324397450 f0:7d:68:08:f2:59 192.168.5.163 D-Link930L 01:f0:7d:68:08:f2:59 > 1324397424 f0:7d:68:02:fb:d2 192.168.5.162 D-Link930 01:f0:7d:68:02:fb:d2 > 1324397377 00:14:d1:f0:a6:d0 192.168.5.116 TV-IP110W 01:00:14:d1:f0:a6:d0 > 1324397377 00:14:d1:f1:2b:89 192.168.5.143 TV-IP312W 01:00:14:d1:f1:2b:89 > > Hosts file /home/config/macaddr > root@debian:/home/config# cat macaddr > 00:14:D1:F1:2B:89,TV-IP312W,192.168.5.160,20m > 00:14:D1:F0:A6:D0,TV-IP110W,192.168.5.161,20m > F0:7D:68:02:FB:D2,D-Link930,192.168.5.162,20m > F0:7D:68:08:F2:59,D-Link930L,192.168.5.163,20m > > Configuration: /etc/dnsmasq.conf > interface=br0 > expand-hosts > domain=my.home > dhcp-range=192.168.5.50,192.168.5.150,20m > dhcp-hostsfile=/home/config/macaddr > dhcp-lease-max=30 > dhcp-authoritative > > Have anyone seen this behavior before, is the cam's at fault? > > > Regards, > > Classee > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss >