Device leases more than one address

Benjamin Wiechman benw at meltel.com
Tue May 13 14:36:25 UTC 2008


I have a customer who is pulling multiple leases on a subnet with one
device.

lease 209.237.101.83 {
  starts 5 2008/05/09 11:08:52;
  ends 5 2008/05/09 21:32:29;
  tstp 5 2008/05/09 21:32:29;
  binding state free;
  hardware ethernet 00:16:b6:3f:dd:62;
  uid "\001\000\026\266?\335b";
}
lease 209.237.101.15 {
  starts 6 2008/05/10 11:38:35;
  ends 6 2008/05/10 17:55:15;
  tstp 6 2008/05/10 17:55:15;
  binding state free;
  hardware ethernet 00:16:b6:3f:dd:62;
  uid "\001\000\026\266?\335b";
}
lease 209.237.101.63 {
  starts 0 2008/05/11 17:52:27;
  ends 0 2008/05/11 17:55:15;
  tstp 0 2008/05/11 17:55:15;
  binding state free;
  hardware ethernet 00:16:b6:3f:dd:62;
  uid "\001\000\026\266?\335b";
}
lease 209.237.101.37 {
  starts 2 2008/05/13 12:46:54;
  ends 2 2008/05/13 12:49:43;
  tstp 2 2008/05/13 12:49:43;
  binding state free;
  hardware ethernet 00:16:b6:3f:dd:62;
  uid "\001\000\026\266?\335b";
}
lease 209.237.101.24 {
  starts 2 2008/05/13 12:49:43;
  ends 3 2008/05/14 12:49:43;
  binding state active;
  next binding state free;
  hardware ethernet 00:16:b6:3f:dd:62;
  uid "\001\000\026\266?\335b";
}

And I'm seeing stuff like this in the logs... 
May 11 12:55:15 dhcp1 dhcpd: DHCPDISCOVER from 00:16:b6:3f:dd:62 via
209.237.101.254 May 11 12:55:15 dhcp1 dhcpd: DHCPOFFER on 209.237.101.30 to
00:16:b6:3f:dd:62 via 209.237.101.254 May 11 12:55:15 dhcp1 dhcpd: uid lease
209.237.101.37 for client 00:16:b6:3f:dd:62 is duplicate on 209.237.101/24
May 11 12:55:15 dhcp1 dhcpd: DHCPREQUEST for 209.237.101.30 (10.0.1.3) from
00:16:b6:3f:dd:62 via 209.237.101.254 May 11 12:55:15 dhcp1 dhcpd: DHCPACK
on 209.237.101.30 to 00:16:b6:3f:dd:62 via 209.237.101.254 May 12 07:40:15
dhcp1 dhcpd: DHCPREQUEST for 209.237.101.30 from 00:16:b6:3f:dd:62 via eth0
May 12 07:40:15 dhcp1 dhcpd: DHCPACK on 209.237.101.30 to 00:16:b6:3f:dd:62
via eth0 May 12 07:49:44 dhcp1 dhcpd: DHCPDISCOVER from 00:16:b6:3f:dd:62
via 209.237.101.254 May 12 07:49:44 dhcp1 dhcpd: DHCPOFFER on 209.237.101.37
to 00:16:b6:3f:dd:62 via 209.237.101.254 May 12 07:49:44 dhcp1 dhcpd: uid
lease 209.237.101.24 for client 00:16:b6:3f:dd:62 is duplicate on
209.237.101/24 May 12 07:49:44 dhcp1 dhcpd: DHCPREQUEST for 209.237.101.37
(10.0.1.3) from 00:16:b6:3f:dd:62 via 209.237.101.254 May 12 07:49:44 dhcp1
dhcpd: DHCPACK on 209.237.101.37 to 00:16:b6:3f:dd:62 via 209.237.101.254
May 12 19:49:44 dhcp1 dhcpd: uid lease 209.237.101.24 for client
00:16:b6:3f:dd:62 is duplicate on 209.237.101/24 May 12 19:49:44 dhcp1
dhcpd: DHCPREQUEST for 209.237.101.37 from 00:16:b6:3f:dd:62 via eth0 May 12
19:49:44 dhcp1 dhcpd: DHCPACK on 209.237.101.37 to 00:16:b6:3f:dd:62 via
eth0

Config:

authoritative;                  # Respect
ddns-update-style none;         # No ddns updates
ddns-updates off;
log-facility local0;            # logging

min-lease-time 28800;           # 8 hours
default-lease-time 86400;       # 24 hours
max-lease-time 86400;           # 24 hours

one-lease-per-client true;
deny duplicates;                
deny bootp;                     
ping-check false;               

option domain-name-servers 1.2.3.4, 1.2.3.5; option domain-name
"domain.com";


subnet 209.237.101.0 netmask 255.255.255.0 {
        option routers 209.237.101.254;
        option broadcast-address 209.237.101.255;
        option subnet-mask 255.255.255.0;
        pool {
                range 209.237.101.13 209.237.101.134;
                range 209.237.101.136 209.237.101.208;
                range 209.237.101.210 209.237.101.253;
        }

        host XXXX {
                hardware ethernet 00:0c:42:0a:1f:60;
                fixed-address 209.237.101.1;
                }
# ETC...
}

I am aware that it is recommended that the host entries be global - these
are entries for network hardware that is not easily moved and will break a
lot of other things if the IP changes so I felt it made more sense to tie it
to the appropriate subnet. The customer in question is not a known host and
should receive an address from the pool.

What could cause this? Is it likely that it is bad firmware or something on
the customer router in question?

I'm running an older version of dhcpd (dhcp-3.0.5-7.el5) on CentOS5. 

Ben Wiechman




More information about the dhcp-users mailing list