No client hardware address?

Ashley M. Kirchner ashley at pcraft.com
Wed Oct 24 21:13:36 UTC 2007


    Let me start off by saying I highly doubt this is a DHCP problem.  I 
repeat, I do NOT suspect DHCP at all here.

    Having said that...  I have one machine on the network that when 
first turned on will request an IP as I would expect it would:

dhcpd: DHCPDISCOVER from 00:08:74:2d:fc:27 via eth1
dhcpd: DHCPOFFER on 192.168.1.139 to 00:08:74:2d:fc:27 (dellscan) via eth1
dhcpd: Added new forward map from flatbed.int.pcraft.com to 192.168.1.139
dhcpd: added reverse map from 139.1.168.192.in-addr.arpa. to 
flatbed.int.pcraft.com
dhcpd: DHCPREQUEST for 192.168.1.139 (192.168.1.1) from 
00:08:74:2d:fc:27 (dellscan) via eth1
dhcpd: DHCPACK on 192.168.1.139 to 00:08:74:2d:fc:27 (dellscan) via eth1


    But then, several hours later, when the lease expires, I would start 
seeing these messages show up for about 3 to 5 seconds then stop:

dhcpd: DHCPINFORM from 192.168.1.139 via eth1
dhcpd: DHCPACK to 192.168.1.139 (<no client hardware address>) via eth1
dhcpd: DHCPINFORM from 192.168.1.139 via eth1
dhcpd: DHCPACK to 192.168.1.139 (<no client hardware address>) via eth1
dhcpd: DHCPINFORM from 192.168.1.139 via eth1
dhcpd: DHCPACK to 192.168.1.139 (<no client hardware address>) via eth1


    So, can anyone think of why the machine would quit sending it's 
hardware address?  A reboot will fix the problem ... every time.  Only 
to re-appear again when the lease expires hours later...

-- 
W | It's not a bug - it's an undocumented feature.
  +--------------------------------------------------------------------
  Ashley M. Kirchner <mailto:ashley at pcraft.com>   .   303.442.6410 x130
  IT Director / SysAdmin / Websmith             .     800.441.3873 x130
  Photo Craft Imaging                       .     3550 Arapahoe Ave. #6
  http://www.pcraft.com ..... .  .    .       Boulder, CO 80303, U.S.A. 



More information about the dhcp-users mailing list