PXEboot with Netgear router
-
@gabbas Well unless I missed something, this entire config file is commented out. So I can guess it doesn’t work as you need it. Let me grab a demo one.
Lets start with this one. Update the 192.168.1.24 address to match your fog server IP address. Move the other config file out of the dnsmasq directory and save this one as ltsp.conf and then restart dnsmasq. FWIW: This config file is only for bios based computer, if you want uefi we need to change a few things. Dual booting may require you update dnsmasq to version 2.76.
# Don't function as a DNS server: port=0 # Log lots of extra information about DHCP transactions. log-dhcp # Set the root directory for files available via FTP. tftp-root=/tftpboot # Disable re-use of the DHCP servername and filename fields as extra # option space. That's to avoid confusing some old or broken DHCP clients. dhcp-no-override # The boot filename, Server name, Server Ip Address dhcp-boot=undionly.kpxe,,192.168.112.24 # PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds. pxe-prompt="Booting FOG Client", 1 dhcp-range=192.168.112.24,proxy -
@gabbas Many thanks for your quick response…I have made the changes but getting the error when try to restart dnsmasq:
fog@fog:/etc/dnsmasq.d$ sudo nano ltsp.conf fog@fog:/etc/dnsmasq.d$ ls ltsp.conf ltsp.conf.save README fog@fog:/etc/dnsmasq.d$ sudo service dnsmasq restart * Restarting DNS forwarder and DHCP server configuration syntax check[fail] fog@fog:/etc/dnsmasq.d$ -
@gabbas I think ltsp.conf.save should be removed, right? as its the same as lstfp.conf…
-
@gabbas For dnsmasq, you need to move all files you don’t want it to look at out of its config directory. If its there it will read it.
As for the syntax error tail /var/log/messages to see what it didn’t like.
-
@george1421 Yes…after removing the other files ,dnsmaq restarted okay…
fog@fog:/etc/dnsmasq.d$ sudo service dnsmasq restart * Restarting DNS forwarder and DHCP server dnsmasq [ OK ] fog@fog:/etc/dnsmasq.d$ ls ltsp.conf README fog@fog:/etc/dnsmasq.d$ -
@gabbas but I am getting the same message “No boot file received” …I really appreciate your assistance.
-
@gabbas OK now that we (think) we know you have a good configuration file.
The next steps are to:
- Install tcpdump on your FOG server.
- Run the following command on the fog server:
tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011 - Pxe boot the target computer until you reach the error.
- Back on the tcpdump command press ctrl-c to exit it out.
- Post the pcap file here for review.
That pcap file will tell us what is going down the wire.
-
@george1421 Many thanks…will update the results here later on when.
-
@george1421 said in PXEboot with Netgear router:
tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011
Hi george, When I run the above command on fog, i get nothing apart from: (I also boot the target machine at the same time):
fog@fog:~$ tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011 tcpdump: fog@fog:~$ -
@gabbas You might have to do sudo before the tcpdump. But if the fog server can hear the dhcp request it should put what it hears in the output.pcap file.
-
@george1421 Can you please see the file attached…Many thanks…I know I am bothering you too much…much appreciated.0_1488316537931_issue.pcap
-
@gabbas I’m sorry to tell you this but there are no dhcp packets in that capture. But there are others. SO I can tell you did not use the tcpdump command as I posted. That command should have only included the dhcp discussions.
Also just to reconfirm the dhcp server, fog server, and pxe booting computer are on the same IP subnet, right?
We are here to help, so it is no bother. I can tell you if it was a bother, I would not be here. I know we can get this worked out if we can get a solid dhcp packet capture.
-
@george1421 Thanks. Yes I conform fog server, router and pxe client are on the same subnet…(192.168.1.0/24). I ran the tcpdump command as you posted…but nothing happens…see the out put when I run this command:
fog@fog:~$ sudo tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011 [sudo] password for fog: fog@fog:~$ ifconfigDoes router’s IP address need to be put somewhere?
-
@gabbas Are you running that tcpdump command as root or the fog user?
If what you are seeing is true (the content of the output.pcap) file being 0 bytes then that also indicates that your fog server isn’t seeing any dhcp requests so dnsmasq will never send out the dhcp option 67 file name.
I can tell you that the command I posted does work, so I’m not sure why its not capturing things in your environment.
One idea, does your FOG server have more than 1 ethernet adapter?
-
@george1421 Yes I also tried to run as root. The client only has 1 NIC…I dont know what’s really missing…
-
@gabbas Something seems to be wrong here with tcpdump on your FOG server. After starting it you should see at least one or two lines of information. Something like this:
fog@fog:~$ sudo tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011 [sudo] password for fog: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytesThe command sits there and waits. Leave it like this and fire up your client till you see the error message on the client. Then stop tcpdump (Ctrl+c) and upload the output.pcap file to the forums.
-
@Sebastian-Roth …I think something is missing in my configuration…Good thing is we are getting a server soon so that will take care of DHCP…I will update the outcome here asap…many thanks…You guys are great…I have Fog setup (which I manage in out department at a university) and it works there like a charm without an issue…I dont know why its not working here…But I will figure it out…(with your assistance…)
