dnsmasq: failed to bind DHCP server socket: Address already in use
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have a box setup as a PXE server.
The interface that will provide DHCP leases is eno3.
dnsmasq is installed and provides tftp service
** bind is not installed - Ubunutu 18.04 **
Error: dnsmasq: failed to bind DHCP server socket: Address already in use
However, netstat indicates dnsmasq has control of port 67. (DHCP)
Could someone tell me why I get this error?
netplan yaml, ifconfig, netstat -aunp and dnsmasq run error here:
root@pxebooter:~# dnsmasq
dnsmasq: failed to bind DHCP server socket: Address already in use
root@pxebooter:~# more /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: config: disabled
network:
version: 2
# renderer: networkd
ethernets:
eno1:
addresses: [10.1.9.199/24]
gateway4: 10.1.9.254
nameservers:
addresses: [205.171.3.65,205.171.2.65]
dhcp4: false
eno2:
addresses: [10.1.100.11/24]
gateway4: 10.1.100.100
dhcp4: false
optional: false
eno3:
addresses: [10.1.200.1/24]
gateway4: 10.1.200.1
dhcp4: false
optional: false
root@pxebooter:~# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.1.9.199 netmask 255.255.255.0 broadcast 10.1.9.255
inet6 fe80::1618:77ff:fe60:c571 prefixlen 64 scopeid 0x20<link>
ether 14:18:77:60:c5:71 txqueuelen 1000 (Ethernet)
RX packets 7695 bytes 1124240 (1.1 MB)
RX errors 0 dropped 742 overruns 0 frame 0
TX packets 2133 bytes 228533 (228.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 94
eno2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 14:18:77:60:c5:72 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 95
eno3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 14:18:77:60:c5:73 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 97
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 130 bytes 10266 (10.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 130 bytes 10266 (10.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@pxebooter:~# grep -v '^#' /etc/dnsmasq.conf
port=0
interface=eno3
dhcp-range=100.1.200.50,10.1.200.150,12h
dhcp-boot=pxelinux.0
enable-tftp
tftp-root=/home/pxe
tftp-no-fail
dhcp-lease-max=99
dhcp-leasefile=/home/pxe/leases
dhcp-authoritative
dhcp-script=/bin/echo
root@pxebooter:~# netstat -aunp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 15360 0 127.0.0.53:53 0.0.0.0:* 1356/systemd-resolv
udp 33600 0 0.0.0.0:67 0.0.0.0:* 1877/dnsmasq
udp 0 0 0.0.0.0:69 0.0.0.0:* 1877/dnsmasq
udp6 0 0 :::69 :::* 1877/dnsmasq
root@pxebooter:~# tftp localhost
tftp> get test.txt
Received 17 bytes in 0.0 seconds
tftp> quit
root@pxebooter:~# dnsmasq
dnsmasq: failed to bind DHCP server socket: Address already in use
root@pxebooter:~# dnsmasq -h
dnsmasq
edited Aug 13 at 18:02
roaima
40.3k547110
asked Aug 13 at 16:35
user3242295
61
add a comment |Â
up vote
0
down vote
favorite
I have a box setup as a PXE server.
The interface that will provide DHCP leases is eno3.
dnsmasq is installed and provides tftp service
** bind is not installed - Ubunutu 18.04 **
Error: dnsmasq: failed to bind DHCP server socket: Address already in use
However, netstat indicates dnsmasq has control of port 67. (DHCP)
Could someone tell me why I get this error?
netplan yaml, ifconfig, netstat -aunp and dnsmasq run error here:
root@pxebooter:~# dnsmasq
dnsmasq: failed to bind DHCP server socket: Address already in use
root@pxebooter:~# more /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: config: disabled
network:
version: 2
# renderer: networkd
ethernets:
eno1:
addresses: [10.1.9.199/24]
gateway4: 10.1.9.254
nameservers:
addresses: [205.171.3.65,205.171.2.65]
dhcp4: false
eno2:
addresses: [10.1.100.11/24]
gateway4: 10.1.100.100
dhcp4: false
optional: false
eno3:
addresses: [10.1.200.1/24]
gateway4: 10.1.200.1
dhcp4: false
optional: false
root@pxebooter:~# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.1.9.199 netmask 255.255.255.0 broadcast 10.1.9.255
inet6 fe80::1618:77ff:fe60:c571 prefixlen 64 scopeid 0x20<link>
ether 14:18:77:60:c5:71 txqueuelen 1000 (Ethernet)
RX packets 7695 bytes 1124240 (1.1 MB)
RX errors 0 dropped 742 overruns 0 frame 0
TX packets 2133 bytes 228533 (228.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 94
eno2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 14:18:77:60:c5:72 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 95
eno3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 14:18:77:60:c5:73 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 97
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 130 bytes 10266 (10.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 130 bytes 10266 (10.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@pxebooter:~# grep -v '^#' /etc/dnsmasq.conf
port=0
interface=eno3
dhcp-range=100.1.200.50,10.1.200.150,12h
dhcp-boot=pxelinux.0
enable-tftp
tftp-root=/home/pxe
tftp-no-fail
dhcp-lease-max=99
dhcp-leasefile=/home/pxe/leases
dhcp-authoritative
dhcp-script=/bin/echo
root@pxebooter:~# netstat -aunp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 15360 0 127.0.0.53:53 0.0.0.0:* 1356/systemd-resolv
udp 33600 0 0.0.0.0:67 0.0.0.0:* 1877/dnsmasq
udp 0 0 0.0.0.0:69 0.0.0.0:* 1877/dnsmasq
udp6 0 0 :::69 :::* 1877/dnsmasq
root@pxebooter:~# tftp localhost
tftp> get test.txt
Received 17 bytes in 0.0 seconds
tftp> quit
root@pxebooter:~# dnsmasq
dnsmasq: failed to bind DHCP server socket: Address already in use
root@pxebooter:~# dnsmasq -h
dnsmasq
edited Aug 13 at 18:02
roaima
40.3k547110
asked Aug 13 at 16:35
user3242295
61
1
Who has the port before you start dnsmasq?
– RalfFriedl
Aug 13 at 17:08
It appears that something has already started dnsmasq and you are attempting to start it again on the same port, which is failing as the port is already in use. If dnsmasq is already started and running why do you need to run it again? If you need to restart dnsmasq, you should find out what is starting it for you and handle it through that (possibly netplan or systemd).
– GracefulRestart
Aug 13 at 22:21
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a box setup as a PXE server.
The interface that will provide DHCP leases is eno3.
dnsmasq is installed and provides tftp service
** bind is not installed - Ubunutu 18.04 **
Error: dnsmasq: failed to bind DHCP server socket: Address already in use
However, netstat indicates dnsmasq has control of port 67. (DHCP)
Could someone tell me why I get this error?
netplan yaml, ifconfig, netstat -aunp and dnsmasq run error here:
root@pxebooter:~# dnsmasq
dnsmasq: failed to bind DHCP server socket: Address already in use
root@pxebooter:~# more /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: config: disabled
network:
version: 2
# renderer: networkd
ethernets:
eno1:
addresses: [10.1.9.199/24]
gateway4: 10.1.9.254
nameservers:
addresses: [205.171.3.65,205.171.2.65]
dhcp4: false
eno2:
addresses: [10.1.100.11/24]
gateway4: 10.1.100.100
dhcp4: false
optional: false
eno3:
addresses: [10.1.200.1/24]
gateway4: 10.1.200.1
dhcp4: false
optional: false
root@pxebooter:~# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.1.9.199 netmask 255.255.255.0 broadcast 10.1.9.255
inet6 fe80::1618:77ff:fe60:c571 prefixlen 64 scopeid 0x20<link>
ether 14:18:77:60:c5:71 txqueuelen 1000 (Ethernet)
RX packets 7695 bytes 1124240 (1.1 MB)
RX errors 0 dropped 742 overruns 0 frame 0
TX packets 2133 bytes 228533 (228.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 94
eno2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 14:18:77:60:c5:72 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 95
eno3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 14:18:77:60:c5:73 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 97
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 130 bytes 10266 (10.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 130 bytes 10266 (10.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@pxebooter:~# grep -v '^#' /etc/dnsmasq.conf
port=0
interface=eno3
dhcp-range=100.1.200.50,10.1.200.150,12h
dhcp-boot=pxelinux.0
enable-tftp
tftp-root=/home/pxe
tftp-no-fail
dhcp-lease-max=99
dhcp-leasefile=/home/pxe/leases
dhcp-authoritative
dhcp-script=/bin/echo
root@pxebooter:~# netstat -aunp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 15360 0 127.0.0.53:53 0.0.0.0:* 1356/systemd-resolv
udp 33600 0 0.0.0.0:67 0.0.0.0:* 1877/dnsmasq
udp 0 0 0.0.0.0:69 0.0.0.0:* 1877/dnsmasq
udp6 0 0 :::69 :::* 1877/dnsmasq
root@pxebooter:~# tftp localhost
tftp> get test.txt
Received 17 bytes in 0.0 seconds
tftp> quit
root@pxebooter:~# dnsmasq
dnsmasq: failed to bind DHCP server socket: Address already in use
root@pxebooter:~# dnsmasq -h
dnsmasq
edited Aug 13 at 18:02
roaima
40.3k547110
asked Aug 13 at 16:35
user3242295
61
I have a box setup as a PXE server.
The interface that will provide DHCP leases is eno3.
dnsmasq is installed and provides tftp service
** bind is not installed - Ubunutu 18.04 **
Error: dnsmasq: failed to bind DHCP server socket: Address already in use
However, netstat indicates dnsmasq has control of port 67. (DHCP)
Could someone tell me why I get this error?
netplan yaml, ifconfig, netstat -aunp and dnsmasq run error here:
root@pxebooter:~# dnsmasq
dnsmasq: failed to bind DHCP server socket: Address already in use
root@pxebooter:~# more /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: config: disabled
network:
version: 2
# renderer: networkd
ethernets:
eno1:
addresses: [10.1.9.199/24]
gateway4: 10.1.9.254
nameservers:
addresses: [205.171.3.65,205.171.2.65]
dhcp4: false
eno2:
addresses: [10.1.100.11/24]
gateway4: 10.1.100.100
dhcp4: false
optional: false
eno3:
addresses: [10.1.200.1/24]
gateway4: 10.1.200.1
dhcp4: false
optional: false
root@pxebooter:~# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.1.9.199 netmask 255.255.255.0 broadcast 10.1.9.255
inet6 fe80::1618:77ff:fe60:c571 prefixlen 64 scopeid 0x20<link>
ether 14:18:77:60:c5:71 txqueuelen 1000 (Ethernet)
RX packets 7695 bytes 1124240 (1.1 MB)
RX errors 0 dropped 742 overruns 0 frame 0
TX packets 2133 bytes 228533 (228.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 94
eno2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 14:18:77:60:c5:72 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 95
eno3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 14:18:77:60:c5:73 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 97
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 130 bytes 10266 (10.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 130 bytes 10266 (10.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@pxebooter:~# grep -v '^#' /etc/dnsmasq.conf
port=0
interface=eno3
dhcp-range=100.1.200.50,10.1.200.150,12h
dhcp-boot=pxelinux.0
enable-tftp
tftp-root=/home/pxe
tftp-no-fail
dhcp-lease-max=99
dhcp-leasefile=/home/pxe/leases
dhcp-authoritative
dhcp-script=/bin/echo
root@pxebooter:~# netstat -aunp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 15360 0 127.0.0.53:53 0.0.0.0:* 1356/systemd-resolv
udp 33600 0 0.0.0.0:67 0.0.0.0:* 1877/dnsmasq
udp 0 0 0.0.0.0:69 0.0.0.0:* 1877/dnsmasq
udp6 0 0 :::69 :::* 1877/dnsmasq
root@pxebooter:~# tftp localhost
tftp> get test.txt
Received 17 bytes in 0.0 seconds
tftp> quit
root@pxebooter:~# dnsmasq
dnsmasq: failed to bind DHCP server socket: Address already in use
root@pxebooter:~# dnsmasq -h
dnsmasq
dnsmasq
edited Aug 13 at 18:02
roaima
40.3k547110
asked Aug 13 at 16:35
user3242295
61
edited Aug 13 at 18:02
roaima
40.3k547110
asked Aug 13 at 16:35
user3242295
61
edited Aug 13 at 18:02
roaima
40.3k547110
edited Aug 13 at 18:02
roaima
40.3k547110
edited Aug 13 at 18:02
roaima
40.3k547110
40.3k547110
asked Aug 13 at 16:35
user3242295
61
asked Aug 13 at 16:35
user3242295
61
asked Aug 13 at 16:35
user3242295
61
61
1
Who has the port before you start dnsmasq?
– RalfFriedl
Aug 13 at 17:08
It appears that something has already started dnsmasq and you are attempting to start it again on the same port, which is failing as the port is already in use. If dnsmasq is already started and running why do you need to run it again? If you need to restart dnsmasq, you should find out what is starting it for you and handle it through that (possibly netplan or systemd).
– GracefulRestart
Aug 13 at 22:21
add a comment |Â
1
Who has the port before you start dnsmasq?
– RalfFriedl
Aug 13 at 17:08
It appears that something has already started dnsmasq and you are attempting to start it again on the same port, which is failing as the port is already in use. If dnsmasq is already started and running why do you need to run it again? If you need to restart dnsmasq, you should find out what is starting it for you and handle it through that (possibly netplan or systemd).
– GracefulRestart
Aug 13 at 22:21
1
1
Who has the port before you start dnsmasq?
– RalfFriedl
Aug 13 at 17:08
Who has the port before you start dnsmasq?
– RalfFriedl
Aug 13 at 17:08
It appears that something has already started dnsmasq and you are attempting to start it again on the same port, which is failing as the port is already in use. If dnsmasq is already started and running why do you need to run it again? If you need to restart dnsmasq, you should find out what is starting it for you and handle it through that (possibly netplan or systemd).
– GracefulRestart
Aug 13 at 22:21
It appears that something has already started dnsmasq and you are attempting to start it again on the same port, which is failing as the port is already in use. If dnsmasq is already started and running why do you need to run it again? If you need to restart dnsmasq, you should find out what is starting it for you and handle it through that (possibly netplan or systemd).
– GracefulRestart
Aug 13 at 22:21
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
dnsmasq is already running, and it's listening on port 67, which is why you get that message. If you stop the dnsmasq service, you'll be able to run it by hand.
answered Aug 13 at 18:31
Tim Kennedy
13.5k22949
Good point. The thing that made me think it wasn't running was I hooked up a computer to the eno3 port and it did not receive a DHCP lease. Is there anyway to trace the process of the DHCP request/response? Currently the requesting computer just hangs waiting for a lease. (dnsmasq not running would be a reasonable excuse for not getting a dhcp lease.) However that doesn't appear to be the issue here.
– user3242295
Aug 14 at 1:38
any idea whyifconfigdoesn't show the IP addresses onen02anden03? One thing I would try is havingtcpdumplisten onen03and seeing if you are even seeing the DHCP request. Then work from there. But the missing IP on en03 may be an issue.
– Tim Kennedy
Aug 14 at 15:23
add a comment |Â
up vote
0
down vote
Well, this is embarrassing.
The reason eno3 is unable to bind to a network address is my network address is wrong. I should have looked at the syslog first.
Aug 14 10:47:52 pxebooter systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: DHCP range 10.1.200.150 -- 100.1.200.50 is not consistent with netmask 255.255.255.0
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: no address range available for DHCP request via eno3
Apparently 10.x.x.x and 100.x.x.x don't fall within the range of the /24 subnet mask.
I don't want to admit how much time I wasted because I didn't notice an extra zero.
Thank you all for your help.
answered Aug 15 at 0:08
user3242295
61
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
dnsmasq is already running, and it's listening on port 67, which is why you get that message. If you stop the dnsmasq service, you'll be able to run it by hand.
answered Aug 13 at 18:31
Tim Kennedy
13.5k22949
Good point. The thing that made me think it wasn't running was I hooked up a computer to the eno3 port and it did not receive a DHCP lease. Is there anyway to trace the process of the DHCP request/response? Currently the requesting computer just hangs waiting for a lease. (dnsmasq not running would be a reasonable excuse for not getting a dhcp lease.) However that doesn't appear to be the issue here.
– user3242295
Aug 14 at 1:38
any idea whyifconfigdoesn't show the IP addresses onen02anden03? One thing I would try is havingtcpdumplisten onen03and seeing if you are even seeing the DHCP request. Then work from there. But the missing IP on en03 may be an issue.
– Tim Kennedy
Aug 14 at 15:23
add a comment |Â
up vote
1
down vote
dnsmasq is already running, and it's listening on port 67, which is why you get that message. If you stop the dnsmasq service, you'll be able to run it by hand.
answered Aug 13 at 18:31
Tim Kennedy
13.5k22949
Good point. The thing that made me think it wasn't running was I hooked up a computer to the eno3 port and it did not receive a DHCP lease. Is there anyway to trace the process of the DHCP request/response? Currently the requesting computer just hangs waiting for a lease. (dnsmasq not running would be a reasonable excuse for not getting a dhcp lease.) However that doesn't appear to be the issue here.
– user3242295
Aug 14 at 1:38
any idea whyifconfigdoesn't show the IP addresses onen02anden03? One thing I would try is havingtcpdumplisten onen03and seeing if you are even seeing the DHCP request. Then work from there. But the missing IP on en03 may be an issue.
– Tim Kennedy
Aug 14 at 15:23
add a comment |Â
up vote
1
down vote
up vote
1
down vote
dnsmasq is already running, and it's listening on port 67, which is why you get that message. If you stop the dnsmasq service, you'll be able to run it by hand.
answered Aug 13 at 18:31
Tim Kennedy
13.5k22949
dnsmasq is already running, and it's listening on port 67, which is why you get that message. If you stop the dnsmasq service, you'll be able to run it by hand.
answered Aug 13 at 18:31
Tim Kennedy
13.5k22949
answered Aug 13 at 18:31
Tim Kennedy
13.5k22949
answered Aug 13 at 18:31
Tim Kennedy
13.5k22949
answered Aug 13 at 18:31
Tim Kennedy
13.5k22949
13.5k22949
Good point. The thing that made me think it wasn't running was I hooked up a computer to the eno3 port and it did not receive a DHCP lease. Is there anyway to trace the process of the DHCP request/response? Currently the requesting computer just hangs waiting for a lease. (dnsmasq not running would be a reasonable excuse for not getting a dhcp lease.) However that doesn't appear to be the issue here.
– user3242295
Aug 14 at 1:38
any idea whyifconfigdoesn't show the IP addresses onen02anden03? One thing I would try is havingtcpdumplisten onen03and seeing if you are even seeing the DHCP request. Then work from there. But the missing IP on en03 may be an issue.
– Tim Kennedy
Aug 14 at 15:23
add a comment |Â
Good point. The thing that made me think it wasn't running was I hooked up a computer to the eno3 port and it did not receive a DHCP lease. Is there anyway to trace the process of the DHCP request/response? Currently the requesting computer just hangs waiting for a lease. (dnsmasq not running would be a reasonable excuse for not getting a dhcp lease.) However that doesn't appear to be the issue here.
– user3242295
Aug 14 at 1:38
any idea whyifconfigdoesn't show the IP addresses onen02anden03? One thing I would try is havingtcpdumplisten onen03and seeing if you are even seeing the DHCP request. Then work from there. But the missing IP on en03 may be an issue.
– Tim Kennedy
Aug 14 at 15:23
Good point. The thing that made me think it wasn't running was I hooked up a computer to the eno3 port and it did not receive a DHCP lease. Is there anyway to trace the process of the DHCP request/response? Currently the requesting computer just hangs waiting for a lease. (dnsmasq not running would be a reasonable excuse for not getting a dhcp lease.) However that doesn't appear to be the issue here.
– user3242295
Aug 14 at 1:38
Good point. The thing that made me think it wasn't running was I hooked up a computer to the eno3 port and it did not receive a DHCP lease. Is there anyway to trace the process of the DHCP request/response? Currently the requesting computer just hangs waiting for a lease. (dnsmasq not running would be a reasonable excuse for not getting a dhcp lease.) However that doesn't appear to be the issue here.
– user3242295
Aug 14 at 1:38
any idea why
ifconfig doesn't show the IP addresses on en02 and en03? One thing I would try is having tcpdump listen on en03 and seeing if you are even seeing the DHCP request. Then work from there. But the missing IP on en03 may be an issue.– Tim Kennedy
Aug 14 at 15:23
any idea why
ifconfig doesn't show the IP addresses on en02 and en03? One thing I would try is having tcpdump listen on en03 and seeing if you are even seeing the DHCP request. Then work from there. But the missing IP on en03 may be an issue.– Tim Kennedy
Aug 14 at 15:23
add a comment |Â
up vote
0
down vote
Well, this is embarrassing.
The reason eno3 is unable to bind to a network address is my network address is wrong. I should have looked at the syslog first.
Aug 14 10:47:52 pxebooter systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: DHCP range 10.1.200.150 -- 100.1.200.50 is not consistent with netmask 255.255.255.0
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: no address range available for DHCP request via eno3
Apparently 10.x.x.x and 100.x.x.x don't fall within the range of the /24 subnet mask.
I don't want to admit how much time I wasted because I didn't notice an extra zero.
Thank you all for your help.
answered Aug 15 at 0:08
user3242295
61
add a comment |Â
up vote
0
down vote
Well, this is embarrassing.
The reason eno3 is unable to bind to a network address is my network address is wrong. I should have looked at the syslog first.
Aug 14 10:47:52 pxebooter systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: DHCP range 10.1.200.150 -- 100.1.200.50 is not consistent with netmask 255.255.255.0
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: no address range available for DHCP request via eno3
Apparently 10.x.x.x and 100.x.x.x don't fall within the range of the /24 subnet mask.
I don't want to admit how much time I wasted because I didn't notice an extra zero.
Thank you all for your help.
answered Aug 15 at 0:08
user3242295
61
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Well, this is embarrassing.
The reason eno3 is unable to bind to a network address is my network address is wrong. I should have looked at the syslog first.
Aug 14 10:47:52 pxebooter systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: DHCP range 10.1.200.150 -- 100.1.200.50 is not consistent with netmask 255.255.255.0
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: no address range available for DHCP request via eno3
Apparently 10.x.x.x and 100.x.x.x don't fall within the range of the /24 subnet mask.
I don't want to admit how much time I wasted because I didn't notice an extra zero.
Thank you all for your help.
answered Aug 15 at 0:08
user3242295
61
Well, this is embarrassing.
The reason eno3 is unable to bind to a network address is my network address is wrong. I should have looked at the syslog first.
Aug 14 10:47:52 pxebooter systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: DHCP range 10.1.200.150 -- 100.1.200.50 is not consistent with netmask 255.255.255.0
Aug 14 10:49:02 pxebooter dnsmasq-dhcp[2769]: no address range available for DHCP request via eno3
Apparently 10.x.x.x and 100.x.x.x don't fall within the range of the /24 subnet mask.
I don't want to admit how much time I wasted because I didn't notice an extra zero.
Thank you all for your help.
answered Aug 15 at 0:08
user3242295
61
answered Aug 15 at 0:08
user3242295
61
answered Aug 15 at 0:08
user3242295
61
answered Aug 15 at 0:08
user3242295
61
61
add a comment |Â
add a comment |Â
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f462349%2fdnsmasq-failed-to-bind-dhcp-server-socket-address-already-in-use%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Who has the port before you start dnsmasq?
– RalfFriedl
Aug 13 at 17:08
It appears that something has already started dnsmasq and you are attempting to start it again on the same port, which is failing as the port is already in use. If dnsmasq is already started and running why do you need to run it again? If you need to restart dnsmasq, you should find out what is starting it for you and handle it through that (possibly netplan or systemd).
– GracefulRestart
Aug 13 at 22:21