Differences
This shows you the differences between two versions of the page.
|
appnote:userclass [2011/01/27 21:03] mcb30 created |
appnote:userclass [2011/03/24 11:32] mcb30 |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| One important practical application of the DHCP User Class is to break the infinite loop when using [[:howto:chainloading|PXE chainloading]]. In this use case, the DHCP server is set to hand out the iPXE binary [[http://boot.ipxe.org/undionly.kpxe|undionly.kpxe]] as the default boot filename for legacy PXE clients, with the "real" boot parameters being handed out only for requests from iPXE clients. | One important practical application of the DHCP User Class is to break the infinite loop when using [[:howto:chainloading|PXE chainloading]]. In this use case, the DHCP server is set to hand out the iPXE binary [[http://boot.ipxe.org/undionly.kpxe|undionly.kpxe]] as the default boot filename for legacy PXE clients, with the "real" boot parameters being handed out only for requests from iPXE clients. | ||
| - | For more complex configurations, you may wish to customise the DHCP User Class sent by iPXE. You can do this by changing the ''user-class'' setting. For example, an embedded script might contain: | + | For more complex configurations, you may wish to customise the DHCP User Class sent by iPXE. You can do this by changing the ''[[:cfg:user-class]]'' setting. For example, an embedded [[:scripting|script]] might contain: |
| #!ipxe | #!ipxe | ||
