Your message dated Tue, 13 Oct 2009 17:02:05 +0000
with message-id <[email protected]>
and subject line Bug#523787: fixed in dnsmasq 2.51-1
has caused the Debian Bug report #523787,
regarding dnsmasq: Usage of /etc/ethers appears to conflict with etherwake
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
523787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523787
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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?
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?
Thanks in advance,
CC
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dnsmasq depends on:
ii adduser 3.110 add and remove users and groups
ii dnsmasq-base 2.45-1 A small caching DNS proxy and DHCP
ii netbase 4.34 Basic TCP/IP networking system
dnsmasq recommends no packages.
Versions of packages dnsmasq suggests:
pn resolvconf <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dnsmasq
Source-Version: 2.51-1
We believe that the bug you reported is fixed in the latest version of
dnsmasq, which is due to be installed in the Debian FTP archive:
dnsmasq-base_2.51-1_i386.deb
to pool/main/d/dnsmasq/dnsmasq-base_2.51-1_i386.deb
dnsmasq_2.51-1.diff.gz
to pool/main/d/dnsmasq/dnsmasq_2.51-1.diff.gz
dnsmasq_2.51-1.dsc
to pool/main/d/dnsmasq/dnsmasq_2.51-1.dsc
dnsmasq_2.51-1_all.deb
to pool/main/d/dnsmasq/dnsmasq_2.51-1_all.deb
dnsmasq_2.51.orig.tar.gz
to pool/main/d/dnsmasq/dnsmasq_2.51.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon Kelley <[email protected]> (supplier of updated dnsmasq package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Fri, 4 Oct 2009 14:01:14 +0000
Source: dnsmasq
Binary: dnsmasq dnsmasq-base
Architecture: source i386 all
Version: 2.51-1
Distribution: unstable
Urgency: low
Maintainer: Simon Kelley <[email protected]>
Changed-By: Simon Kelley <[email protected]>
Description:
dnsmasq - A small caching DNS proxy and DHCP/TFTP server
dnsmasq-base - A small caching DNS proxy and DHCP/TFTP server
Closes: 523787 528762
Changes:
dnsmasq (2.51-1) unstable; urgency=low
.
* New upstream.
* Bump standards-version to 3.8.2 (no changes needed).
* Ignore files named *.dpkg-old, *.dpkg-new and *.dpkg-dist
in /etc/dnsmasq.d
* Provide a facility in /etc/default/dnsmasq to disable dnsmasq's
interaction with the resolvconf package. This is needed because
setting "resolv-file" in /etc/dnsmasq.conf won't override a
file given on the command line from resolvconf. (closes: #528762)
* Check for duplicate names/addresses in /etc/ethers. (closes: #523787)
* Set the system locale in the environment before invoking dnsmasq,
so that translated messages work, and IDN uses the correct charset.
Checksums-Sha1:
96eb46be7ab225d6f15824157e43ee46307637ac 986 dnsmasq_2.51-1.dsc
92f8a41050dae6eba527414a6a5af746e9d36a71 403937 dnsmasq_2.51.orig.tar.gz
912a34310136c73c6d02265d468ee47469298f0f 15714 dnsmasq_2.51-1.diff.gz
e03a0768839624514ba0ed2b0a9e257d3a833a23 281034 dnsmasq-base_2.51-1_i386.deb
13e63c71fc00fd6c56b6d6423d372f114a76b50d 13854 dnsmasq_2.51-1_all.deb
Checksums-Sha256:
11e78ea7a88074caf6471114bd8ab0cc5fd5b4e813536cd4b62902fe548b881b 986
dnsmasq_2.51-1.dsc
a7de736b4ea54793398538f476a9f477fa2fdf9adf7775b37a499a490623cd14 403937
dnsmasq_2.51.orig.tar.gz
efcb071530e0d6d136a8c56a280fce120ab460539f4340885ac3a31dccfff909 15714
dnsmasq_2.51-1.diff.gz
ead0835b3db1853fa21daaf6930ac416387b45a377123f9689ea65ff890f097c 281034
dnsmasq-base_2.51-1_i386.deb
d69f0f16b78ef3e621f0386ef9e90097ace68713e841e8bef5768731d96ea069 13854
dnsmasq_2.51-1_all.deb
Files:
fcc435ca02dfcc0938ca0fb12e5c1ecd 986 net optional dnsmasq_2.51-1.dsc
98a35f5fae19d3309134a233fb840ec0 403937 net optional dnsmasq_2.51.orig.tar.gz
7b5a5f24cf75cbb1b1576f35d042e73e 15714 net optional dnsmasq_2.51-1.diff.gz
a621d6733e547d2d354e9f3bcc5aebaa 281034 net optional
dnsmasq-base_2.51-1_i386.deb
c05bafb839c24d5e66625f329bbae964 13854 net optional dnsmasq_2.51-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkrUrdgACgkQKPyGmiibgreomgCffKkArx+kyl1sNYyvbGD44jCX
98MAnA59R11zeVppZs5nURtoOhdoRC3w
=SLrp
-----END PGP SIGNATURE-----
--- End Message ---
