This is an old revision of the document!
====== How to configure dnsmasq for gPXE ====== {{ nic.jpeg?237×222|A network card}} ===== Why DNSMasq ===== * It is small and lightweight * Easy to setup (includes its own tftp server) * It may already be running on your linux-based router :-) ===== Defining the gPXE-specific options ===== Add the following settings to your ///etc/dnsmasq.conf// file: dhcp-boot=pxelinux.0 enable-tftp tftp-root=/var/lib/tftpboot for pxe chaining use this: dhcp-match=gpxe,175 dhcp-boot=net:#gpxe,gpxe.pxe dhcp-boot=pxelinux.0 the '#' above is a 'not', not a comment See: http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq.conf.example for more information ===== A potential problem and a fix ===== According to this page: http://blog.nella.org/?p=335 <code> gPXE wants to find the boot filename in the dedicated slot in the reply packet. dnsmasq does something clever/stupid (I’m not sure which) and puts it someplace else. You have to use the –dhcp-no-override option to dnsmasq to make gPXE see the filename. </code> Here is an online version of the [[http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html|man page]] for dnsmasq. it contains this switch explanation: <code> --dhcp-no-override Disable re-use of the DHCP servername and filename fields as extra option space. If it can, dnsmasq moves the boot server and filename information (from dhcp-boot) out of their dedicated fields into DHCP options. This make extra space available in the DHCP packet for options but can, rarely, confuse old or broken clients. This flag forces "simple and safe" behaviour to avoid problems in such a case. </code>
