[Dnsmasq-discuss] Re: Dnsmasq-discuss] Would like to use dnsmasq for cluster booting

[Simon Kelley]

Joe Landman wrote:
> Hi folks:
> 
>   I have been using dnsmasq for a few years within a simple network and 
> some linux clusters.  With the inclusion of the DHCP bits, and the bootp 
> bits, suddenly the idea of replacing that fine bit of work known as the 
> ISC DHCP server seems possible (and quite likely).
> 
>   I have managed to serve some pxelinux.0 files quite nicely.  What I 
> want to do is to serve the nbgrub (network boot grub) bits, and have it 
> read its menu.lst.
> 
>   To make this happen, I need to set option T150 to (nd)/menu.lst .  I 
> am doing this via
> 
>     dhcp-option=150,"(nd)/menu.lst"
> 
>   So after setting this up, nbgrub does boot, but the logs have
> 
> Sep  3 07:40:55 autoinst dnsmasq[11915]: DHCPREQUEST(eth0) 192.168.32.34 
> 00:11:09:cc:d3:e8
> Sep  3 07:40:55 autoinst dnsmasq[11915]: DHCPACK(eth0) 192.168.32.34 
> 00:11:09:cc:d3:e8
> Sep  3 11:40:55 autoinst in.tftpd[11946]: RRQ from 192.168.32.34 
> filename /nbgrub
> Sep  3 11:40:55 autoinst in.tftpd[11946]: tftp: client does not accept 
> options
> Sep  3 11:40:55 autoinst in.tftpd[11947]: RRQ from 192.168.32.34 
> filename /nbgrub
> 
>   and then nothing (e.g. no menu.lst request), and the grub just hangs 
> there.
> 
>   What am I doing wrong?  Will dnsmasq work this way or can it serve 
> only pxelinux like bits?
> 
>   Here are my relevant dnsmasq.conf options:
> 
>     domain=boot.scalableinformatics.com
>     dhcp-range=192.168.32.1,192.168.32.128
>     dhcp-boot=/nbgrub,autoinst,192.168.32.217
>     dhcp-option=150,"(nd)/menu.lst"
> 
>   Thanks!
> 
> Joe
> 
> 

That should all work: the only obvious (potential) problem is the quotes 
in the dhcp-option line. They are not strictly necessary, and will break 
things on earlier dnsmasq versions. They should be OK with 2.22 and 
2.23, at least.

Can you use tcpdump or ethereal to grab the complete DHCPREQUEST and 
DHCPACK packets and send them to me off list? That's by far the easiest 
way to see if the problem is dnsmasq configuration or not.

Cheers,

Simon.