Hi again,

"log-dhcp" in the dnsmasq.conf file rather than the command line works,
I can see all sorts of details about DHCP clients that dnsmasq is
catching, they behave as expected, and that's a useful debug log. 

However, "bootp-dynamic" alone doesn't solve my problem: although
wireshark sees the bootp requests on the interface that's enabled with
the IP that matches the dhcp-host entry that matches the client, dnsmasq
still isn't noticing.

dnsmasq.conf enables the interface:
(tested with only this interface active, to simpify things)

  interface=ens1f0np0

a range is set:

  dhcp-range=interface:ens1f0np0,10.102.0.0,static,12h

and the host is listed:

  dhcp-host=08:00:30:4c:58:47,newdom2282,10.102.0.101

(I have also tried a dynamic range, didn't help, variations on:
dhcp-range=interface:ens1f0np0,10.102.0.129,10.102.0.254,255.255.255.0,12h )

That interface is configured, although it's a /16 rather than a /24 if
that matters:

ens1f0np0: connected to ens1f0np0
        "Broadcom and subsidiaries BCM57414 NetXtreme-E"
        ethernet (bnxt_en), 84:16:0C:5F:89:C0, hw, mtu 9000
        inet4 10.102.0.3/16
        route4 10.102.0.0/16 metric 102
        inet6 fe80::4989:b7ba:89b2:6aa5/64
        route6 fe80::/64 metric 1024

Any ideas appreciated: it seems as if the daemon just isn't getting the
same bootp request as wireshark or dhcpd are.

    thanks,
    Alec

-- 
                               Alec Habig
                     University of Minnesota Duluth
                     Dept. of Physics and Astronomy
                             [email protected]
                   http://neutrino.d.umn.edu/~habig/

_______________________________________________
Dnsmasq-discuss mailing list
[email protected]
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss