Ben Humpert
2015-09-26 16:50:28 UTC
Hi,
I very often get this message and clients cannot connect anymore
because they don't get an IP address offered. Below is the log for one
request
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 available DHCP
range: 192.168.0.200 -- 192.168.0.254
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 client provides
name: BrigittesiPhone
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759
DHCPDISCOVER(eth1.1) 50:7a:55:1a:96:62
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 tags: guest, eth1.1
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 DHCPOFFER(eth1.1)
192.168.0.223 50:7a:55:1a:96:62
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 requested options:
1:netmask, 3:router, 6:dns-server, 15:domain-name,
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 requested options:
119:domain-search, 252
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 next server: 192.168.0.2
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 1
option: 53 message-type 2
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 54 server-identifier 192.168.0.2
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 51 lease-time 1h
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 58 T1 30m
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 59 T2 52m30s
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 1 netmask 255.255.255.0
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 28 broadcast 192.168.0.255
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 6 dns-server 192.168.0.2
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 14
option: 15 domain-name guest.an3k.lan
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 1
option:252 0a
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 3 router 192.168.0.1
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 available DHCP
range: 192.168.0.200 -- 192.168.0.254
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 client provides
name: BrigittesiPhone
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759
DHCPREQUEST(eth1.1) 192.168.0.223 50:7a:55:1a:96:62
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 DHCPNAK(eth1.1)
192.168.0.223 50:7a:55:1a:96:62 no leases left
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 broadcast response
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 1
option: 53 message-type 6
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 54 server-identifier 192.168.0.2
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 14
option: 56 message 6e:6f:20:6c:65:61:73:65:73:20:6c:65:66:74
The file /var/lib/misc/dnsmasq.leases shows two leases active for the
given range (192.168.0.200 - 254), thus it is very confusing why I get
the "no leases left" error.
Dnsmasq 2.68 is running on Debian 14.04. The server has two physical
NICs (one for management VLAN and second for virtual NICs only) and 10
virtual NICs for each VLAN.
I very often get this message and clients cannot connect anymore
because they don't get an IP address offered. Below is the log for one
request
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 available DHCP
range: 192.168.0.200 -- 192.168.0.254
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 client provides
name: BrigittesiPhone
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759
DHCPDISCOVER(eth1.1) 50:7a:55:1a:96:62
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 tags: guest, eth1.1
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 DHCPOFFER(eth1.1)
192.168.0.223 50:7a:55:1a:96:62
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 requested options:
1:netmask, 3:router, 6:dns-server, 15:domain-name,
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 requested options:
119:domain-search, 252
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 next server: 192.168.0.2
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 1
option: 53 message-type 2
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 54 server-identifier 192.168.0.2
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 51 lease-time 1h
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 58 T1 30m
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 59 T2 52m30s
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 1 netmask 255.255.255.0
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 28 broadcast 192.168.0.255
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 6 dns-server 192.168.0.2
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 14
option: 15 domain-name guest.an3k.lan
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 1
option:252 0a
Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 3 router 192.168.0.1
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 available DHCP
range: 192.168.0.200 -- 192.168.0.254
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 client provides
name: BrigittesiPhone
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759
DHCPREQUEST(eth1.1) 192.168.0.223 50:7a:55:1a:96:62
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 DHCPNAK(eth1.1)
192.168.0.223 50:7a:55:1a:96:62 no leases left
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 broadcast response
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 1
option: 53 message-type 6
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 4
option: 54 server-identifier 192.168.0.2
Sep 26 18:40:31 dns dnsmasq-dhcp[37159]: 1029998759 sent size: 14
option: 56 message 6e:6f:20:6c:65:61:73:65:73:20:6c:65:66:74
The file /var/lib/misc/dnsmasq.leases shows two leases active for the
given range (192.168.0.200 - 254), thus it is very confusing why I get
the "no leases left" error.
Dnsmasq 2.68 is running on Debian 14.04. The server has two physical
NICs (one for management VLAN and second for virtual NICs only) and 10
virtual NICs for each VLAN.