On Tue, May 18, 2010 at 11:32 PM, Jedrzej Kalinowski <kalin...@iem.pw.edu.pl> wrote: > 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?
>From my reading of the RFC that field is optional. That explains why gPXE doesn't set the field. ISC's man page says the option can be used to implement a secondary DHCP server that is only used if the primary is not responding. The secondary only responds to requests if the secs field is larger than a threshold, giving the primary a chance to respond first. I believe gPXE already supports a priority DHCP option that could be used in the same way. The secondary server should have a lower priority than the primary, so gPXE chooses the primary when available. Joshua: I think you know the DHCP code and how priority works. Any ideas? Setting the secs field shouldn't be difficult though. Stefan _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
