I am looking to support PXE installs, which apparently require specific DHCP options....I would really like to keep my DD-WRT as my DHCP server. Which is successfully, resolving hostnames and aliases (A and CNAME).
Can anyone point be to the correct reference. Currently am trying to install ubuntu, fedora and windows (ick) accross the network. _________________ sparticus
dhcp-boot=[net:<network-id>,]<filename>,[<servername>[,<server address>]]
Set BOOTP options to be returned by the DHCP server. Server name and address are optional: if not provided, the name is left empty, and the address set to the address of the machine running dnsmasq. If dnsmasq is providing a TFTP service (see --enable-tftp ) then only the filename is required here to enable network booting. If the optional network-id(s) are given, they must match for this configuration to be sent. Note that network-ids are prefixed by "net:" to distinguish them.
Hi, I have set this up and I do not seem to be getting the correct information sent to my machine, actually, it doesn't look like it's getting any at all.
I started up a VMWare virtual box, and the PXE boot tries to get an IP from DHCP, but just times out. I have it bridged so it should be getting it's information from my dd-wrt router.
I have the option
Code:
dhcp-boot=pxelinux.0,slurms,192.168.1.70
That machine is set to get the same IP everytime. I also have tftp-hpa running with the correct files in place.
Is there anyway to test the DHCP to see if it's handing out the correct pxe information? A debug of sorts?
Not sure where to go from here. Any suggestions on how to make the dnsmasq actually hand out the right thing? Is there any way dnsmasq and the default dhcp server could be clashing?
I've read through the DNSMasq man page but I still don't quite understand what I need to do to translate the above into proper syntax for the DNSMasq options box in DD-WRT's web admin interface. From both the posts above and the DNSMasq man page I got as far as this:
Quote:
dhcp-boot = bflash.2800,,192.168.1.4 (<--static IP of tftp server running on a different machine than DD-WRT)
...but when I boot the machine with that single DNSMasq option it understandably complains that it didn't get the boot protocol data.
Might anyone provide some clue how I can get DNSMasq to send the proper options? I'd appreciate the help... thanks!
Last edited by valuequest on Sun Nov 09, 2008 13:46; edited 10 times in total
Joined: 04 Dec 2006 Posts: 16 Location: United States : southeastern Virginia
Posted: Sun Nov 09, 2008 3:56 Post subject:
Hello luky37...
OK I've edited my post ^ which I hope clarifies somewhat I'm trying to do here. I am looking to PXE-boot the file named bflash.2800 currently sitting on 192.168.1.4 in /tftpboot. My DD-WRT router is sitting in between the two machines and I'm trying to figure out how to configure it to serve out all the the proper DHCP data for the task...
You don't neet to have the 'enable-tftp' option in dnsmasq, because the TFTP-Server will run on the 192.168.1.4, which would be a Linux/Windows machine where a tftp server is installed, and has the bflash.2800 in its root directory.
Quote:
dhcp-boot = bflash.2800,,192.168.1.4 (<--static IP of tftp server running on a different machine than DD-WRT)
this is absolutly enough (apart from activating DNSmasq as DHCP Server - go to Status/LAN and look at the line DHCP-Daemon (DHCP Status). It should be DNSMasq).
The DHCP Server will pass the following information to your boot client:
A TFTP server at 192.168.1.4 has the bootfile bflash.2800 in his TFTP root directory where you can boot from.
Then you need of course a tftp daemon running on that machine.
For Linux i would recommend tftpd-hpa (i think you will able to log verbose) and for windows tftpd32.
Keep in mind that the bootfile bflash.2800 must not be a floppy image! It must be a kernel image where a machine can boot from.
For PXE i would recommend PXELINUX with MEMDISK for booting a floppy image.
I have tried all different combinations and the client refuses to attempt connection to anything other than the router address (192.168.1.1). I have tried option 54 Server Identifier and DNSMasq will not send what I put. It will only send the router's address. Should it not take my direct input of options over it's own defaults?[/code]
