[Novalug] dnsmasq question--solved completely
larkoc at iges.org
Tue Jan 5 12:00:20 EST 2010
Megan Larko wrote:
Answering my own question here.
Running dnsmasq with the default user (root?) got me the dhcp and tftp. The server file
permissions had to be 755 for directories (myOS/) and 644 for the files (the initrd.. and the
vmlinuz...) in the /tftpboot directory.
Solving my below-mentioned "Unknown keyword in config file" message, Google is indeed your friend.
I had a line #default OS1 in my diskless boot config file. The response on Google:
indicated that in syslinux, a comment symbol # _MUST_ be followed by a space.
I made that one change and my box got its dhcp lease, tftp information, had permission and booted
the file perfectly after fixing the comment line.
> Bryan J. Smith wrote:
> As a couple of astute LUGgers wrote to me, the issue was that my firewall was blocking dnsmasq
> functionality. The /etc/services file indicates that tftp uses default ports 68 and dhcp uses
> default ports 69 _both_ UDP and TCP. I had the UDP blocked. Now that the fw was dropped then
> adjusted, back up, I can now successfully get the DHCP lease and the tftp boot occurs.
> My new issue is tangently-related to dnsmasq. In my original /etc/dnsmasq.conf file I had the
> program running as UID "nobody" and GID "nobody". That did not seem to give me permission to read
> the diskless boot files in my /tftpboot directory (pxelinux.0 and the pxelinux.cfg dir). I
> commented-out the dnsmasq.conf "run as" directive. After changing ownership from "larkoc" to
> "root", I am now able to see the boot files (I still have one "Unknown keyword in config file." in
> my boot, but that is not dnsmasq-related).
> For security, should I change the ownership of the boot files to "nobody"?
> Thank you List for your help!
More information about the Novalug