[Dnsmasq-discuss] DHCP doesn't seem to respond to requests(?)

[dnsmasq at lovelady.com]

Thank you very much for your rapid reply, Jasui!!  See inline.


Dennis Lovelady
--
"Little chance of rain, and no chance of temperature."
        -- weather forecaster Rick Jeffries of KTKT, Tucson, AZ 


> > My configuration is simple for now:

# (latest)
domain-needed
bogus-priv
expand-hosts
domain=lovelady.com
dhcp-range=192.168.0.150,192.168.0.249,72h
dhcp-host=00:23:8b:8a:ad:70,192.168.0.249
log-dhcp

> 1. turn on logging by adding "log-dhcp" and tail -f .../messages
> 2. run "tcpdump -i eth0 port bootpc or port bootps" on server

Stopped iptables and flushed with -F on both systems.

Nothing in /var/log/messages.  tcpdump output:
tcpdump -i eth0 port bootpc or port bootps
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes
21:16:47.089977 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request [|bootp]
21:16:49.999600 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request [|bootp]
21:16:57.003601 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request [|bootp]
21:17:07.006508 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request [|bootp]
21:17:09.999333 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request [|bootp]
21:17:16.002246 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request [|bootp]
21:17:28.008047 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request [|bootp]
21:17:43.000168 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request [|bootp]
21:18:00.010982 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request [|bootp]

Double Verbose looks like:
21:22:19.998312 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto
UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request [|bootp]

Still nothing in /var/log/messages.

> > iptables -A INPUT -p UDP --dport bootpc -j ACCEPT || die
> > iptables -A INPUT -p UDP --dport bootps -j ACCEPT || die
> >
> On server?

Yes.  Sorry.

> Can't you turn off all firewalling on client and server?
> (unconnecting them from "dangerous world" first ;-)
> 
> You can also test it adding tap interface (can be in a bridge with eth0)
> and then running something like:
> qemu -net nic,model=pcnet -net tap,ifname=tap0,script=no,downscript=no
> -boot n
> ...and watch "tcpdump -i tap0" (br0)

I don't know what this means.  I don't have qemu, and it doesn't seem to be
in the list of packages (per `ipkg list`) available for this server (which
is an ARM embedded device - NAS actually).

I do appreciate the feedback.  Other ideas?