osdir.com
mailing list archive

Subject: Announce: dnsmasq 2.33 - msg#00007

List: network.dns.dnsmasq.general

Date: Prev Next Index Thread: Prev Next Index
Changelog below: there's no pressing need to upgrade unless you want the
external lease database feature, or have a Cisco router.


Cheers,

Simon.


version 2.33
Remove bash-specific shellcode from the Makefile.

Fix breakage with some DHCP relay implementations which
was introduced in 2.28. Believing the source port in
DHCP requests and sending the reply there is sometimes a
bad thing to do, so I've reverted to always sending to
the relay on port 68. Thanks to Daniel Hamlin and Alex
(alde) for bug reports on this.

Moved the SuSe packaging files to contrib. I will no
longer attempt to maintain this in the source tarball. It
will be done externally, in the same way as packaging for
other distros. Suse packages are available from
ftp://ftp.suse.com/pub/people/ug/

Merged patch from Gentoo to honour $LDFLAGS environment.

Fix bug in resolv.conf processing when more than one file
is being checked.

Add --dns-forward-max option.

Warn if --resolv-file flags are ignored because of
--no-resolv. Thanks to Martin F Krafft for spotting this
one.

Add --leasefile-ro option which allows the use of an
external lease database. Many thanks to Steve Horbachuk
for assistance developing this feature.

Provide extra information to lease-change script via its
environment. If the host has a client-id, then
DNSMASQ_CLIENT_ID will be set. Either the lease length (in
DNSMASQ_LEASE_LENGTH) or lease expiry time (in
DNSMASQ_LEASE_EXPIRES) will be set, depending on the
HAVE_BROKEN_RTC compile-time option. This extra
information should make it possible to maintain the lease
database in external storage such as LDAP or a relational
database. Note that while leasefile-ro is set, the script
will be called with "old" events more often, since
changes to the client-id and lease length
(HAVE_BROKEN_RTC) or lease expiry time (otherwise)
are now flagged.

Add contrib/wrt/* which is an example implementation of an
external persistent lease database for *WRT distros with
the nvram command.

Add contrib/wrt/dhcp_release.c which is a small utility
which removes DHCP leases using DHCPRELEASE operation in
the DHCP protocol.


Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

Re: Dnsmasq on a machine that is a DHCP client

Kaspar Fischer wrote: > Hi everybody, > > I have a server in our LAN that runs dnsmasq in order to offer > DHCP to other machines on the LAN. This works usually great, but > sometimes the following happens: On a client machine, > > > ping google.com > ping: cannot resolve google.com: Unknown host > > domain-names are not resolved anymore (but I verified that the > internet itself is accessible: e.g., I can visit Google via > http://216.239.59.103/). On the server itself (the one that > runs dnsmasq), 'ping google.com' works perfectly. > > Now, I suspect the following. The server itself uses DHCP to > obtain an external IP and the IPs of some domain-name servers > to use. So my guess is that when these change, dnsmasq does > somehow not realize it and fails. Could this be the cause of > the problem? Does dnsmasq work on machines that our themselves > DHCP clients? > > (On the other hand it seems strange that our provider changes > the DNS servers, right? Maybe the problem lies somewhere else?) It's possible, but unlikely, that yourproviders are changing nameserver addresses on the fly, but as long as your DHCP client re-writes /etc/resolv.conf when that happens, dnsmasq will cope. It checks the mtime of /etc/resolv.conf and will re-read it automatically if it changes. There will be evidence in the log if this happens. The best way to chase this problem is to enable query-logging in dnsmasq, and look in the system log when the problem occurs. Cheers, Simon. > > Many thanks, > Kaspar > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj@xxxxxxxxxxxxxxxx > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss >

Next Message by Date: click to view message preview

2.33 compile warning wit NO_IPV6

I would suggest to document NO_IPV6 in src/config.h like /* #define HAVE_BROKEN_RTC */ /* #define HAVE_ISC_READER */ /* #define HAVE_DBUS */ Actually it is described only in Changelog. I was not able to pass -DNO_IPV6 to CFLAGS but made a #define on config.h. There is some warnings using NO_IPV6 netlink.c: In function `iface_enumerate': netlink.c:120: warning: label `again' defined but not used netlink.c:102: warning: unused parameter `ipv6_callback' This patch fix 2 warnings but I am unsure about how to fix unused parameter `ipv6_callback' Gilles dnsmasq-2.33-NO_IPV6-warnings.patch Description: Binary data _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj@xxxxxxxxxxxxxxxx http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Previous Message by Thread: click to view message preview

Dnsmasq on a machine that is a DHCP client

Hi everybody, I have a server in our LAN that runs dnsmasq in order to offer DHCP to other machines on the LAN. This works usually great, but sometimes the following happens: On a client machine, > ping google.com ping: cannot resolve google.com: Unknown host domain-names are not resolved anymore (but I verified that the internet itself is accessible: e.g., I can visit Google via http://216.239.59.103/). On the server itself (the one that runs dnsmasq), 'ping google.com' works perfectly. Now, I suspect the following. The server itself uses DHCP to obtain an external IP and the IPs of some domain-name servers to use. So my guess is that when these change, dnsmasq does somehow not realize it and fails. Could this be the cause of the problem? Does dnsmasq work on machines that our themselves DHCP clients? (On the other hand it seems strange that our provider changes the DNS servers, right? Maybe the problem lies somewhere else?) Many thanks, Kaspar

Next Message by Thread: click to view message preview

2.33 compile warning wit NO_IPV6

I would suggest to document NO_IPV6 in src/config.h like /* #define HAVE_BROKEN_RTC */ /* #define HAVE_ISC_READER */ /* #define HAVE_DBUS */ Actually it is described only in Changelog. I was not able to pass -DNO_IPV6 to CFLAGS but made a #define on config.h. There is some warnings using NO_IPV6 netlink.c: In function `iface_enumerate': netlink.c:120: warning: label `again' defined but not used netlink.c:102: warning: unused parameter `ipv6_callback' This patch fix 2 warnings but I am unsure about how to fix unused parameter `ipv6_callback' Gilles dnsmasq-2.33-NO_IPV6-warnings.patch Description: Binary data _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj@xxxxxxxxxxxxxxxx http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by