[Dnsmasq-discuss] New setup. DNS OK, DHCP is silent

[Lovelady, Dennis E.]

> >You're not using the configuration you think you are. If dnsmasq was
> reading a configuration with dhcp-range in >it, it would log that fact at start-
> up. This is also consistent with dnsmasq not listening on port 67.
> >  Maybe a command-line option is sending dnsmasq to a different config-
> file?
> >
> >
> >Cheers,
> >
> >Simon,
> 
> You are correct, Simon.  We're a step closer.
> 
> This strange (to me) setup (on an NAS device, embedded Linux) often (but
> not always) uses /opt/etc/... for configuration data and so on, and it's
> burned me before.  (The great thing about standards: there are so many
> from which to choose!)  I think they just want to mess with my head.  I
> should learn!
> 
> Anyway, I have now set a link:
>     rm /opt/etc/dnsmasq.conf
>     ln -fs /etc/dnsmasq.conf /opt/etc
> 
> and it now reports that it's listending for DHCP requests.  Yeah.  But still no
> joy.
> 
> netstat output is improved:
> 
> netstat -anp|grep dnsmasq
> tcp        0      0 0.0.0.0:53                  0.0.0.0:*                   LISTEN      9915/dnsmasq
> udp        0      0 0.0.0.0:53                  0.0.0.0:*                               9915/dnsmasq
> udp        0      0 0.0.0.0:67                  0.0.0.0:*                               9915/dnsmasq
> unix  2      [ ]         DGRAM                    40072  9915/dnsmasq
> 
> Now listening on port 67.
> 
> But DHCP requests are still not honored.
> 
> Here's the startup now:
> 
> Nov 24 13:47:06 stora-2 dnsmasq[11000]: started, version 2.62 cachesize 150
> Nov 24 13:47:06 stora-2 dnsmasq[11000]: compile time options: IPv6 GNU-
> getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack Nov
> 24 13:47:06 stora-2 dnsmasq-dhcp[11000]: DHCP, IP range 192.168.158.64 --
> 192.168.158.191, lease time 1d Nov 24 13:47:06 stora-2 dnsmasq[11000]:
> reading /etc/resolv.conf Nov 24 13:47:06 stora-2 dnsmasq[11000]: using
> nameserver 192.168.158.1#53 Nov 24 13:47:06 stora-2 dnsmasq[11000]:
> ignoring nameserver 127.0.0.1 - local interface Nov 24 13:47:06 stora-2
> dnsmasq[11000]: read /etc/hosts - 2 addresses
> 
> 
> Here's my tcpdump output, run on that very server.
> 
> tcpdump -ni eth0 'udp port 67 and udp port 68'
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes
> 13:38:49.076695 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> [|bootp]
> 13:39:08.078646 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> [|bootp]
> 13:39:27.078484 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> [|bootp]
> 13:40:02.078788 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> [|bootp]
> 13:40:09.078597 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> [|bootp]
> 13:40:20.078097 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> [|bootp]
> 13:40:27.078534 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> [|bootp]
> 
> 7 packets captured
> 8 packets received by filter
> 0 packets dropped by kernel
> 
> I can promise that iptables is not running... what else might stand in the
> way?

Please disregard.

Somehow on boot-up, this device created a new copy of iptables, from somewhere.  After I had once again stopped iptables, flushed the tables, deleted the binaries... then DHCP started working.  It'll break again when I reboot.

I shall set about finding and crippling the process that insists on bestowing its idea of protection on me.

Gads, that's worse than those sites that make you set passwords nobody can remember so that you can see some text file that's publicly available, and then force you to change your password every time you sign on (seems like).  Let's blame the lawyers.

Dennis
<BR>_____________________________________________________________
<FONT size=2><BR>
DTCC DISCLAIMER: This email and any files transmitted with it are
confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email
in error, please notify us immediately and delete the email and any
attachments from your system. The recipient should check this email
and any attachments for the presence of viruses.  The company
accepts no liability for any damage caused by any virus transmitted
by this email.</FONT>