[Dnsmasq-discuss] TFTP boot

[Simon Kelley]

Philippe Faure wrote:
> Hello,
> 
> I am trying to us DNSMASQ to install Ubuntu Server a new machine, but  
> it isn't working. HEre is what I have
> 
> dhcp-boot=pxelinux.0,fileserver,192.168.0.34
> enable-tftp
> tftp-root=/var/lib/tftpboot
> 
> dir /var/lib/tftpboot/
> drwxrwxrwx  3 nobody nogroup 4.0K 2009-04-17 12:08 .
> drwxr-xr-x 37 root   root    4.0K 2009-06-08 15:22 ..
> lrwxrwxrwx  1 nobody nogroup   33 2009-06-08 15:24 pxelinux.0 ->  
> ubuntu-installer/amd64/pxelinux.0
> lrwxrwxrwx  1 nobody nogroup   35 2009-06-08 15:24 pxelinux.cfg ->  
> ubuntu-installer/amd64/pxelinux.cfg
> drwxr-xr-x  3 nobody nogroup 4.0K 2009-04-17 12:08 ubuntu-installer
> -rw-r--r--  1 nobody nogroup   56 2009-04-17 12:08 version.info
> 
> Contents of pxelinux.cfg
> include ubuntu-installer/amd64/boot-screens/menu.cfg
> default ubuntu-installer/amd64/boot-screens/vesamenu.c32
> prompt 0
> timeout 0
> 
> DNSMASQ.log results
> Aug 20 16:12:26 dnsmasq[4418]: TFTP sent /var/lib/tftpboot/pxelinux.0  
> to 192.168.0.60
> Aug 20 16:12:26 dnsmasq[4418]: TFTP error 0 TFTP Aborted received from  
> 192.168.0.60
> Aug 20 16:12:26 dnsmasq[4418]: TFTP failed sending  
> /var/lib/tftpboot/pxelinux.0 to 192.168.0.60
> Aug 20 16:12:26 dnsmasq[4418]: TFTP sent /var/lib/tftpboot/pxelinux.0  
> to 192.168.0.60
> 
> The display on the new box states the following:
> PXE-T04: Unsupoort Request from 192.168.0.60
> PXE-E36: Error Received from TFTP server
> PXE-M0F: Exiting NVIDIA Boot Agent
> 
> Does anyone have any idea of what the problem is, or where to start  
> looking to fix it? I know that the new box is getting the IP address  
> from the dHCP server, 192.168.0.60, so it is something with the TFTP  
> server.
> 
> Thank you
> 
> Philippe
What version of dnsmasq are you using? It's possible that the boot agent 
is requesting a transfer in netascii mode, and this will fail in dnsmasq 
versions before 2.42. Is the failure message really misspelled or is 
that a copying error? dnsmasq will return the error

unsupported request from <IP address>

to the client but I would expect it to log the error too.


Exec summary: if you're using a version before 2.42, update. otherwise 
try and get a packet capture of the interaction using tcpdump and send 
it to me.

Cheers,

Simon.