[gPXE] 'secs' value not increased in subsequent DHCP requests

[Joshua Oreman]

On Wed, May 19, 2010 at 1:24 AM, Stefan Hajnoczi <stefanha at gmail.com> wrote:
> 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?

Priority is a gPXE-specific encapsulated option (option number 175.1)
that determines how multiple DHCP offers received ~simultaneously are
ordered. For it to have any effect, either the higher-priority
DHCPOFFER needs to be received before the lower-priority DHCPACK (if
the lower-priority DHCPOFFER includes PXE extensions or the
gPXE-specific "ignore PXE extensions" option), or the higher-priority
DHCPOFFER needs to be received within two seconds of the
lower-priority DHCPOFFER (if not). The default priority is 0 if
unspecified; negative priority is not supported.

If this wouldn't work for your application, a patch to set the secs
field would probably be pretty straightforward.

-- Josh

>
> Setting the secs field shouldn't be difficult though.
>
> Stefan
>