I’m having no success in running dnsmasq as an IPv4 DCHP server for my local network. I’ve managed to at least get the server to start if I set NM_CONTROLLED=no for the LAN ethernet interface. Without that it fails because NetworkManager has seized the bootps port (67). With wireshark, I can see the incoming DHCP discover broadcast packets, but there is no reply. I can see that dnsmasq is listening on the appropriate port:
Jan 13 18:54:44 omega-3x.local dnsmasq[5444]: listening on enp5s0(#3): 192.168.44.1
lsof -i :67
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
NetworkMa 1461 root 30u IPv4 43535 0t0 UDP omega-3x.local:bootpc->omega-3g.local:bootps
dnsmasq 5444 dnsmasq 4u IPv4 179368 0t0 UDP *:bootps
And here are the non-comment lines of my dnsmasq.conf (other pre-assigned hosts deleted):
domain-needed
bogus-priv
local=/local/
listen-address=192.168.44.1
listen-address=127.0.0.1
bind-interfaces
dhcp-authoritative
dhcp-range=192.168.44.160,192.168.44.191,24h#dhcp-host=D8:5E:D3:8A:11:0D, 192.168.44.51, omega-3x
#dhcp-host=F4:26:79:E1:27:BA, 192.168.44.50, omega-3xw
#dhcp-host=90:E6:BA:31:19:C5, 10.0.0.48, omega-3a
dhcp-option=option:ntp-server,0.0.0.0 # = this machine
dhcp-option=2,-21600 # Central Standard Time
dhcp-option=6,0.0.0.0 # domain-name-servers
dhcp-option=15,local # Domain name#dhcp-host=D8:5E:D3:8A:11:0D, 192.168.44.51, omega-3x
#dhcp-host=F4:26:79:E1:27:BA, 192.168.44.50, omega-3xw
#dhcp-host=90:E6:BA:31:19:C5, 10.0.0.48, omega-3a
dhcp-host=00:1E:EC:0C:22:35, 192.168.44.52, omega-3p
This is basically the same configuration that I have working in a CentOS 6 server I’m trying to replace. I do have all firewalls turned off. I don’t know what is keeping this from working.