openslx-ng/ipxe.git/src/include/gpxe/dhcp.h, branch v0.9.9Fork of ipxe; additional commands and featureshttps://git.openslx.org/openslx-ng/ipxe.git/atom/src/include/gpxe/dhcp.h?h=v0.9.92009-08-11T23:27:08+00:00[dhcp] Fall back to using the hardware address to populate the chaddr field2009-08-11T23:27:08+00:00Michael Brown2009-08-11T22:44:04+00:00urn:sha1:444d5550a70fef7735ed1821a0e6f8410f0e03ef
For IPoIB, the chaddr field is too small (16 bytes) to contain the
20-byte IPoIB link-layer address. RFC4390 mandates that we should
pass an empty chaddr field and rely on the DHCP client identifier
instead. This has many problems, not least of which is that a client
identifier containing an IPoIB link-layer address is not very useful
from the point of view of creating DHCP reservations, since the QPN
component is assigned at runtime and may vary between boots.
Leave the DHCP client identifier as-is, to avoid breaking existing
setups as far as possible, but expose the real hardware address (the
port GUID) via the DHCP chaddr field, using the broadcast flag to
instruct the DHCP server not to use this chaddr value as a link-layer
address.
This makes it possible (at least with ISC dhcpd) to create DHCP
reservations using host declarations such as:
host duckling {
fixed-address 10.252.252.99;
hardware unknown-32 00:02:c9:02:00:25:a1:b5;
}
[legal] Add a selection of FILE_LICENCE declarations2009-05-18T07:33:25+00:00Michael Brown2009-05-01T14:41:06+00:00urn:sha1:c44a193d0d147ed6f98741124569864e516e9d4b
Add FILE_LICENCE declarations to almost all files that make up the
various standard builds of gPXE.
[pxe] Obey lists of PXE Boot Servers and associated Discovery Control bits2009-02-05T09:34:32+00:00Michael Brown2009-02-05T09:30:32+00:00urn:sha1:881f1f59ef2abb9b0e9c5a56730a22fb9094b84c
Various combinations of options 43.6, 43.7 and 43.8 dictate which
servers we send Boot Server Discovery requests to, and which servers
we should accept responses from. Obey these options, and remove the
explicit specification of a single Boot Server from start_pxebs() and
dependent functions.
[pxe] Skip PXE boot server discovery if directed to do so2009-02-05T09:34:05+00:00Michael Brown2009-02-03T02:46:06+00:00urn:sha1:ff2b308506ed67f6cc007356f6a10358c6ee48f1
Option 43.6 can direct us to skip PXE boot server discovery and just
perform a standard DHCP filename boot.
[dhcp] Send user class in DHCP requests2009-02-01T20:06:09+00:00Michael Brown2009-02-01T20:06:09+00:00urn:sha1:4502c04360c997c48b0b00e4bf4142cd63760306[dhcp] Split PXE menuing code out of dhcp.c2009-02-01T01:21:40+00:00Michael Brown2009-01-31T07:36:05+00:00urn:sha1:e65afc4b10552ec9ac7de2f0d924b96bc71aaad0
The DHCP client code now implements only the mechanism of the DHCP and
PXE Boot Server protocols. Boot Server Discovery can be initiated
manually using the "pxebs" command. The menuing code is separated out
into a user-level function on a par with boot_root_path(), and is
entered in preference to a normal filename boot if the DHCP vendor
class is "PXEClient" and the PXE boot menu option exists.
[dhcp] Include support for PXE boot menus2009-01-25T21:16:47+00:00Michael Brown2009-01-25T21:16:47+00:00urn:sha1:027c72e0d0e2456ce5fbf7d5284f8ca7d3c94ade
PXE dictates a mechanism for boot menuing, involving prompting the
user with a variable message, waiting for a predefined keypress,
displaying a boot menu, and waiting for a selection.
This breaks the currently desirable abstraction that DHCP is a process
that can happen in the background without any user interaction.
[dhcp] Clarify language surrounding ProxyDHCP2009-01-23T01:47:33+00:00Michael Brown2009-01-23T01:47:33+00:00urn:sha1:3f814f08e50e6ffbe7d87c20dcc68bbc327cdaa4
Remove the lazy assumption that ProxyDHCP == "DHCP with option 60 set
to PXEClient", and explicitly separate the notion of ProxyDHCP from
the notion of packets containing PXE options.
[dhcp] Pass PXE boot menu item to PXE Boot Server2009-01-23T01:13:50+00:00Michael Brown2009-01-23T01:13:50+00:00urn:sha1:76d05a4da0184aea77ba8ca49062a2b26cbbebf4
Pick out the first boot menu item from the boot menu (option 43.9) and
pass it to the boot server as the boot menu item (option 43.71).
Also improve DHCP debug messages to include more details of the
packets being transmitted.
[dhcp] Add preliminary support for PXE Boot Servers2009-01-21T03:43:26+00:00Michael Brown2009-01-21T03:43:26+00:00urn:sha1:6941793416474f68f3dcbbf55258ac35de65026a
Some PXE configurations require us to perform a third DHCP transaction
(in addition to the real DHCP transaction and the ProxyDHCP
transaction) in order to retrieve information from a "Boot Server".
This is an experimental implementation, since the actual behaviour is
not well specified in the PXE spec.