Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
appnote:premature [2018/07/05 21:36] mcb30 |
appnote:premature [2022/12/11 21:03] (current) stappers dnsmasq has dhcp-option for enforcing encapsulation |
||
|---|---|---|---|
| Line 24: | Line 24: | ||
| ===== TFTP server ===== | ===== TFTP server ===== | ||
| - | Work in progress WIP FIXME text to ADD | + | To enable the TFTP server set |
| + | |||
| + | # Enable dnsmasq's built-in TFTP server | ||
| + | enable-tftp | ||
| + | |||
| + | # Set the root directory for files availble via FTP. | ||
| + | tftp-root=/var/lib/tftpboot/ | ||
| ===== PXE chainloading ===== | ===== PXE chainloading ===== | ||
| Line 30: | Line 37: | ||
| {{ :clipart:chain.jpeg?200x120|A chain}} | {{ :clipart:chain.jpeg?200x120|A chain}} | ||
| - | To use [[:howto:chainloading|PXE chainloading]], you need to set up ISC dhcpd to hand out [[http://boot.ipxe.org/undionly.kpxe|undionly.kpxe]] to legacy PXE clients, and then hand out the "real" boot configuration only to iPXE clients. You can do this by telling dnsmasq to use different configurations based on the DHCP user class: | + | To use [[:howto:chainloading|PXE chainloading]], you need to set up dnsmasq to hand out [[http://boot.ipxe.org/undionly.kpxe|undionly.kpxe]] to legacy PXE clients, and then hand out the "real" boot configuration only to iPXE clients. You can do this by telling dnsmasq to use different configurations based on the DHCP user class: |
| dhcp-boot=undionly.kpxe | dhcp-boot=undionly.kpxe | ||
| Line 42: | Line 49: | ||
| There are several DHCP options that are specific to iPXE and that are not recognised by the standard ISC dhcpd installation. To add support for these options, place the following at the start of your ''/etc/dhcpd.conf'': | There are several DHCP options that are specific to iPXE and that are not recognised by the standard ISC dhcpd installation. To add support for these options, place the following at the start of your ''/etc/dhcpd.conf'': | ||
| + | |||
| + | Dnsmasq can do //"encapsulation"// with configuration item ''dhcp-option''. | ||
| Work in progress WIP FIXME text to REMOVE | Work in progress WIP FIXME text to REMOVE | ||
| + | |||
| + | ISC dhcpd syntax: | ||
| option space ipxe; | option space ipxe; | ||
| Line 99: | Line 110: | ||
| Work in progress WIP FIXME | Work in progress WIP FIXME | ||
| + | |||
| + | NOTE this is again: Can dnsmasq encapsulate further options in option 175? | ||
| The PXE specification requires iPXE to wait for replies from a ProxyDHCP server before booting. If you are not using a ProxyDHCP server, then this creates an unnecessary delay of several seconds. You can eliminate this delay using: | The PXE specification requires iPXE to wait for replies from a ProxyDHCP server before booting. If you are not using a ProxyDHCP server, then this creates an unnecessary delay of several seconds. You can eliminate this delay using: | ||
| Line 109: | Line 122: | ||
| FIXME | FIXME | ||
| + | |||
| + | NOTE another encapsulate option ... | ||
| You can use the feature indicator options to determine whether or not iPXE supports a specific feature. For example, | You can use the feature indicator options to determine whether or not iPXE supports a specific feature. For example, | ||
