[Dnsmasq-discuss] Dnsmasq Stopping In Authoritive Mode

Simon Kelley simon at thekelleys.org.uk
Wed Mar 14 11:58:13 GMT 2007


Bill Aitken wrote:
> 
> We have a wireless segment connected of our firewall, with dnsmasq
> configured to provide DHCP addresses to the wireless clients.  We've
> configured DHCP as  authoritative in order to ensure clients connecting
> always get one of our addresses.  However, when a client connects with
> an IP from another source DNSmasq simply shuts down with no errors in
> the log, other than martian and "wrong network" errors:
> 
> martian source 192.168.2.1 from 192.168.2.100,
> on dev eth1
> 
> then:
> 
> Mar 14 08:52:31 taygate kernel: [53210378.550000] ll header:
> ff:ff:ff:ff:ff:ff:00:05:4e:4b:77:fd:08:06
> Mar 14 08:52:34 taygate dnsmasq[16784]: DHCPREQUEST(eth1)
> 192.168.2.100 00:05:4e:4b:77:fd
> Mar 14 08:52:34 taygate dnsmasq[16784]: DHCPNAK(eth1) 192.168.2.100
> 00:05:4e:4b:77:fd wrong network
> Mar 14 08:53:25 taygate monit[11990]: 'dnsmasq' process is not running
> 
> If I give myself a manual address, then remove the authoritive directive
> I receive an address correctly.
> 
> Has anyone came across this issue before?
>

I'm not aware of this problem coming up before. It looks like an
interseting one.

Please could you provide a least the following information?

1) Version of dnsmasq and Linux kernel in use.
2) Network configuration, output of ifconfig, or (preferably) "ip addr show"
3) Complete dnsmasq configuration, config file and any command-line options.
4) Client in use.
5) Information about any DHCP relay use.


Also, if you can find out where dnsmasq is crashing, that would be very
useful. The easiest procedure goes like this:

1) recompile dnsmasq with "make clean; make CFLAGS=-g"
2) run dnsmasq under gdb: "gdb dnsmasq -d"
3) start dnsmasq: "run"
4) cause crash.
5) run gdb command "bt" to get a stack trace.

Cheers,

Simon.



More information about the Dnsmasq-discuss mailing list