Issues booting to fog using dnsmasq
-
The part that’s weird to me is the fact that it’s not trying to pull the file from the ltsp located server is it?
-
Correct. If you look at the jpegs I attached to an earlier post.
If I change the ltsp.conf to use undionly.0 it boots to network and imediatly gives me file not found. With the conf set as in my last post containing that info, it boots to the Network, goes to the second JPEG then attempts to try downloading default.ipxe from the DHCP server rather than the FOG Server where TFTP is set up and running. And as I stated if I stop dnsmasq on the FOG Server there is nothing else on the network handling Network boots so the systems fail that and go to their HDD.
I will go through the TCPDump steps and post the output.
-
Here is the issue.pcap. I will transfer it to my Windows box and look at it with Wireshark, but figured you guys would find stuff faster than I. Changed extension to .txt since it wouldn’t let me upload .pcap or .tar.gz
[url=“/_imported_xf_attachments/1/1972_issue.txt?:”]issue.txt[/url]
-
Forgot the Destination MAC. It is 78:45:C4:3D:8F:E7
-
Based on what you’re telling us, it sounds like your DHCP server is setup to hand out a next-server and/or filename address.
Could you see about having this disabled?
-
I have run into this issue as well. By doing heavy amounts of research I came to the following conclusions:
[LIST=1]
[]DnsMasq is hard coded to add a .0 to the end of a file. There is no good reason for this. That’s just how it do.
[]There are some PXE clients (computer firmwares) that have issues with it. They assume the “next-server” to be the DHCP unless given a specific Option 66, unlike most other PXE clients that assume the “next-server” to be the same as where they were told to get the boot file. Once again, no good reason for this, just how they do.
[/LIST] -
I checked the only active DHCP server and neither option 66 or option 67 are checked/enabled. I will talk to the vendor that handles our Network to see if there is anywhere else this might be set up.
From need2’s comment it looks like I might just need to have Option 66 set. I was really hoping to not have to touch the DHCP server as I am new to this company and don’t want to push my boundries yet.
-
Your client asks 172.25.5.80 for undionly.kpxe.0 - that’s correct.
And it looks like it gets the file, too.
However you’ve got some ARP issues… (duplicate use of 172.25.100.43 detected!) I’m not sure what that’s about.
So why is it saying file not found when I can see with my eyes that it’s finding the file and getting it?
-
Options 66 and 67 will make your life easier. It’s MUCH more simple than dnsmasq.
When you set those, disable dnsmasq on the FOG server.
-
I was getting all sorts of weird packets from dnsmasq when I was fiddling with it. It looks like it does some really hacky things to inject the extra DHCP code without being a DHCP server.
-
need2 was correct. I tried on some newer systems and it boots properly. My Test machine is older and we only have about 10 in production so I am okay with it not working on those systems till we get them replaced. On our newest systems Dell Optiplex 9020, when it gets to the point where is was trying to go to the DHCP server for the default.ipxe file, it asks for the TFTP server IP. Once I put that in it boots to Fog normally.
I am good with the state I have it right now and will inquire about changing the DHCP options with the Vendor and my Boss.
-
For the older systems, you could try other boot files.
UEFI = .efi files.
BIOS = everything else.No harm in that, now that you know you’re solid with this config. Just back it up, back it up, back it up.
-
Also, I think changing this line will keep you from having to enter in the TFTP server IP manually into each workstation:
You have:
[CODE]pxe-service=X86PC, “Boot from network”, undionly.kpxe[/CODE]Change to:
[CODE]pxe-service=X86PC, “Boot from network”, undionly.kpxe, <tftp-server-ip-goes-here>[/CODE]Reference:
[url]http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html[/url]
