[gPXE] 'secs' value not increased in subsequent DHCP requests
Jedrzej Kalinowski
kalinoj1 at iem.pw.edu.pl
Tue May 18 18:32:24 EDT 2010
Hello,
My dhcp server has the min-secs property set to 2. The result is gPXE not
getting IP adress from the server, because every request sent to it has
field 'secs' set to 0.
May 17 21:06:57 x dhcpd: PACKET from gPXE: ether: 0:50:56:3f:ff:1
PXEClient:Arch:00000:UNDI:002001
May 17 21:06:57 x dhcpd: PACKET from VMware ESXi: ether: 0:50:56:3f:ff:1
May 17 21:06:57 x dhcpd: DISCOVER from ESX-JK via lagg0: 0 secs < 2
May 17 21:06:58 x dhcpd: PACKET from gPXE: ether: 0:50:56:3f:ff:1
PXEClient:Arch:00000:UNDI:002001
May 17 21:06:58 x dhcpd: PACKET from VMware ESXi: ether: 0:50:56:3f:ff:1
May 17 21:06:58 x dhcpd: DISCOVER from ESX-JK via lagg0: 0 secs < 2
May 17 21:07:00 x dhcpd: PACKET from gPXE: ether: 0:50:56:3f:ff:1
PXEClient:Arch:00000:UNDI:002001
May 17 21:07:00 x dhcpd: PACKET from VMware ESXi: ether: 0:50:56:3f:ff:1
May 17 21:07:00 x dhcpd: DISCOVER from ESX-JK via lagg0: 0 secs < 2
May 17 21:07:04 x dhcpd: PACKET from gPXE: ether: 0:50:56:3f:ff:1
PXEClient:Arch:00000:UNDI:002001
May 17 21:07:04 x dhcpd: PACKET from VMware ESXi: ether: 0:50:56:3f:ff:1
May 17 21:07:04 x dhcpd: DISCOVER from ESX-JK via lagg0: 0 secs < 2
According to RFC 1541, subsequent dhcp requests should have the 'secs'
field incremented. However I didn't find such implementation in gPXE code.
Could you comment on this if I'm right and share if you plan to implement
this?
Best regards,
Jedrzej Kalinowski
More information about the gPXE
mailing list