diff options
| author | Joshua Oreman | 2009-12-08 09:40:50 +0100 |
|---|---|---|
| committer | Marty Connor | 2010-01-20 23:15:51 +0100 |
| commit | b1ba80f8fbe2377e992848c3c6e6eb55fbe6d909 (patch) | |
| tree | 7f999145480b9dfdfa8ab094230d395374de3303 /src/include/usr | |
| parent | [pxe] Separate parent PXE API caller from UNDINET driver (diff) | |
| download | ipxe-b1ba80f8fbe2377e992848c3c6e6eb55fbe6d909.tar.gz ipxe-b1ba80f8fbe2377e992848c3c6e6eb55fbe6d909.tar.xz ipxe-b1ba80f8fbe2377e992848c3c6e6eb55fbe6d909.zip | |
[dhcp] Add generic facility for using cached network settings
When a DHCP session is started (using autoboot or a command-line `dhcp
net0'), check whether the new setting use-cached (DHCP option 175.178)
is TRUE; if so, skip DHCP and rely on currently registered
settings. This lets one combine a static IP with autoboot.
Before checking the use-cached setting, call a weak
get_cached_dhcpack() hook that can be implemented by particular builds
of gPXE supporting some fashion of retrieving a cached DHCPACK packet.
If one is available, it is registered as an options source, and then
either that packet's option 175.178 or the user's prior manual
use-cached setting can allow skipping duplicate DHCP.
Using cached packets is not the default because DHCP servers are often
configured to give gPXE different options than they give a vendor PXE
client; in order to break the infinite loop of PXE chaining, one would
need to load a gPXE with an embedded image that does something more
than autoboot.
Signed-off-by: Marty Connor <mdc@etherboot.org>
Diffstat (limited to 'src/include/usr')
0 files changed, 0 insertions, 0 deletions
