Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
appnote:chainload_wds [2015/11/05 14:11] svenx TFTP is primarily slow due to latency, not virtualization. |
appnote:chainload_wds [2015/11/05 14:58] svenx Re-word to refer to PXE NBP section of :settings. |
||
|---|---|---|---|
| Line 46: | Line 46: | ||
| thing that needs to be modified is the DHCP ''next-server'' parameter, | thing that needs to be modified is the DHCP ''next-server'' parameter, | ||
| which will let ''wdsnbp.com'' know which server to communicate with. | which will let ''wdsnbp.com'' know which server to communicate with. | ||
| - | Due to how iPXE handles [[:settings#scopes|configuration setting | + | |
| - | scope]], it is important that the //original// setting is modified. In | + | Be sure to [[:settings#pxe_nbps|set DHCP options]] so that they are |
| - | other words, modify ''netX.dhcp/next-server'' (or use an explicit | + | made available to the PXE NBP. For example, the ''next-server'' |
| - | interface number: ''net0.dhcp/next-server''), not simply the | + | parameter can be set via ''netX/next-server''. |
| - | ''next-server'' or ''netX.net-server'' values. | + | |
| Example iPXE commands to chainload ''wdsnbp.com'': | Example iPXE commands to chainload ''wdsnbp.com'': | ||
| - | set netX.dhcp/next-server ip.of.wds.server | + | set netX/next-server ip.of.wds.server |
| - | imgexec tftp://${netX.dhcp/next-server}/boot/x86/wdsnbp.com | + | imgexec tftp://${netX/next-server}/boot/x86/wdsnbp.com |
| ===== The WDS boot process ===== | ===== The WDS boot process ===== | ||
