====== dnsmasq ====== [[https://thekelleys.org.uk/dnsmasq/doc.html|dnsmasq]] has gained popularity in recent years. It can easily be configured to support iPXE. ===== DHCP proxy ===== If you can't modify your existing dhcp then a proxy is the way to go. It uses ''option 43'' to display a menu and ''UDP port 4011'' for the PXE configuration, while the IP and other information is given by your default DHCP server. To use [[:howto:chainloading|PXE chainloading]], we will configure dnsmasq to give out [[https://boot.ipxe.org/undionly.kpxe|undionly.kpxe]] or [[https://boot.ipxe.org/snponly.efi|snponly.efi]] to legacy PXE clients, and then hand out the "real" boot configuration only to iPXE clients using ''tags''. iPXE feature options will be used to verify that it has all features that we want, see [[:howto:dhcpd#ipxe-specific_options|dhcp page]] for all iPXE-specific options. Things to modify: * ''10.1.1.0'' - your subnet * ''eth0'' - interface to listen on, or switch to bind-dynamic * ''10.1.1.2'' - your tftp server ip * ''http://boot.ipxe.org/demo/boot.php'' - script to run once inside iPXE # Known working dnsmasq version 2.85 config for iPXE proxydhcp usage # Debug logging log-debug # Disable DNS server port=0 # send disable multicast and broadcast discovery, and to download the boot file immediately # DHCP_PXE_DISCOVERY_CONTROL, should be vendor option? Needs more understanding and source dhcp-option=vendor:PXEClient,6,2b # This range(s) is for the public interface, where dnsmasq functions # as a proxy DHCP server providing boot information but no IP leases. # Any ip in the subnet will do, so you may just put your server NIC ip here. dhcp-range=10.1.1.0,proxy interface=eth0 # bind-dynamic - remove interface and use this instead to listen everywhere? # Disable re-use of the DHCP servername and filename fields as extra # option space. That's to avoid confusing some old or broken DHCP clients. dhcp-no-override #dhcp-match=set:,