Strange Client Behavior

David E. Bruce dbruce at uark.edu
Thu Dec 3 23:04:38 UTC 2009


I've got a client on my network that is requesting an IP, receiving it  
from the DHCP server, and then turning around and asking for another  
one within a few minutes.  The server is then providing a second IP.   
The client then proceeds to request both IPs at the normal intervals  
throughout the day.  Here's the log entry:

Nov 25 07:51:13 192.168.1.1 dhcpd: DHCPDISCOVER from 00:1e:4f:a7:e1:c2  
via eth0.222
Nov 25 07:51:14 192.168.1.1 dhcpd: DHCPOFFER on 192.168.72.84 to 00:1e: 
4f:a7:e1:c2 (scasterxp) via eth0.222
Nov 25 07:51:15 192.168.1.1 dhcpd: DHCPREQUEST for 192.168.72.84  
(192.168.1.1) from 00:1e:4f:a7:e1:c2 (scasterxp) via eth0.222
Nov 25 07:51:15 192.168.1.1 dhcpd: DHCPACK on 192.168.72.84 to 00:1e: 
4f:a7:e1:c2 (scasterxp) via eth0.222

Nov 25 07:53:41 192.168.1.1 dhcpd: DHCPDISCOVER from 00:1e:4f:a7:e1:c2  
via eth0.222
Nov 25 07:53:42 192.168.1.1 dhcpd: DHCPOFFER on 192.168.72.188 to  
00:1e:4f:a7:e1:c2 (scasterxp) via eth0.222
Nov 25 07:53:42 192.168.1.1 dhcpd: DHCPREQUEST for 192.168.72.188  
(192.168.1.1) from 00:1e:4f:a7:e1:c2 (scasterxp) via eth0.222
Nov 25 07:53:42 192.168.1.1 dhcpd: DHCPACK on 192.168.72.188 to 00:1e: 
4f:a7:e1:c2 (scasterxp) via eth0.222

Nov 25 09:51:47 192.168.1.1 dhcpd: DHCPREQUEST for 192.168.72.84 from  
00:1e:4f:a7:e1:c2 (scasterxp) via eth0.222
Nov 25 09:51:47 192.168.1.1 dhcpd: DHCPACK on 192.168.72.84 to 00:1e: 
4f:a7:e1:c2 (scasterxp) via eth0.222

Nov 25 09:54:06 192.168.1.1 dhcpd: DHCPREQUEST for 192.168.72.188 from  
00:1e:4f:a7:e1:c2 (scasterxp) via eth0.224
Nov 25 09:54:06 192.168.1.1 dhcpd: DHCPACK on 192.168.72.188 to 00:1e: 
4f:a7:e1:c2 (scasterxp) via eth0.224

Nov 25 11:51:51 192.168.1.1 dhcpd: DHCPREQUEST for 192.168.72.84 from  
00:1e:4f:a7:e1:c2 (scasterxp) via eth0.222
Nov 25 11:51:51 192.168.1.1 dhcpd: DHCPACK on 192.168.72.84 to 00:1e: 
4f:a7:e1:c2 (scasterxp) via eth0.222

Nov 25 11:54:06 192.168.1.1 dhcpd: DHCPREQUEST for 192.168.72.188 from  
00:1e:4f:a7:e1:c2 (scasterxp) via eth0.224
Nov 25 11:54:06 192.168.1.1 dhcpd: DHCPACK on 192.168.72.188 to 00:1e: 
4f:a7:e1:c2 (scasterxp) via eth0.224


As far as I know, there's nothing to prevent the server from providing  
the client with another IP, even though it already has a lease, is  
that correct?  This looks like a client issue to me, but I'd thought  
I'd ask if anyone has seen this before.

Thanks,

David Bruce
Network Engineering Team
University IT Services
(479) 575-2901




More information about the dhcp-users mailing list