Chris Carr wrote: > Package: dnsmasq > Version: 2.45-1 > Severity: normal > > > I am not 100% certain about this bug, so I apologise if I've just > misunderstood something. > > I have a whole bunch of machines on my LAN, each of which has its MAC > address(es) in /etc/ethers along with its name. Each machine's name is > linked to its IP in /etc/hosts. dnsmasq reports that both files are read > successfully: > > Apr 12 13:46:55 baba dnsmasq[6583]: read /etc/hosts - 34 addresses > Apr 12 13:46:55 baba dnsmasq[6583]: read /etc/ethers - 25 addresses > > It all worked fine after I set it up (to replace dhcp3-server and > bind9) - IP addresses were handed out correctly - until I rebooted any > of the machines. At that point it started handing out pool addresses > instead of the ones specified in /etc/hosts. Even after I manually > edited /var/lib/misc/dnsmasq.leases to remove the erroneous leases (and > released the lease from the client), dnsmasq still handed out the same > pool address to each machine instead of its specified address. > > (The reason I'm not sure is because it didn't happen consistently with > every machine - one machine continued to get the correct IP, and I tried > PXE booting on another, which might have confused that case if it > didn't release the lease on failure) > > On advice from a friend I edited /etc/ethers and replaced the names with > the fixed IP addresses from /etc/hosts. This seemed to solve the problem > (though I don't understand why) - but this renders /etc/ethers unusable by > etherwake (which expects a name rather than an IP). > > Am I missing something here? Is there another explanation for dnsmasq > stopping and then restarting successful use of static IPs? Or does it > expect the IPs to be in /etc/ethers?
It should work with <mac address>,<name> pairs in /etc/ethers and <address>,<name> pairs in /etc/hosts. Could you try turning on log-dhcp and send me complete logs which illustrate the problem, also the contents on /etc/ethers and /etc/hosts. (Send to me personally and not the bug-tracker, if you don't want them made public.) > > One thing I have noticed is that lease keep appearing back in > /var/lib/misc/dnsmasq.leases after I manually delete them (and the > client machine remains off). So I think there is something I don't > understand about dnsmasq's operation - where else is it storing this > lease information? > The database is stored internally, the leases file is only ever read at start-up, but written whenever it changes, so to make manual changes, you need to stop dnsmasq, edit the leases file, then restart dnsmasq. Cheers, Simon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
