FOG .33b PXE Boot woes
I did follow the chainloading instructions under the link i provided earlier.
My /tftpboot folder:
fogadmin@FOG2:~$ ls /tftpboot/
boot.txt ipxe.krn pxelinux.0.old snponly.efi undionly.kpxe
default.ipxe memdisk pxelinux.cfg tftpboot vesamenu.c32
fogadmin@FOG2:~$ ls /tftpboot/pxelinux.cfg/
default default~ pxelinux.cfg
[url=“/_imported_xf_attachments/0/648_default pxelinuxcfg.jpg?:”]default pxelinuxcfg.jpg[/url][url=“/_imported_xf_attachments/0/649_ltspconf.jpg?:”]ltspconf.jpg[/url][url=“/_imported_xf_attachments/0/650_default pxelinuxcfg.jpg?:”]default pxelinuxcfg.jpg[/url][url=“/_imported_xf_attachments/0/651_ltspconf.jpg?:”]ltspconf.jpg[/url]
I meant a screenshot of the machine failing to load the pxe boot info.
Did you edit the dnsmaq.conf file? I see it open in the editor there, I recommend leaving those settings alone and only editing the ltsp.conf
dhcp-boot should be
After you make the change, restart the dnsmasq service,
That is probably my fault I will make adjustments on the wiki.
Oh lol sorry.
[quote=“Paul Freeman, post: 25137, member: 23545”]Oh lol sorry.
See the post above this one, I believe the problem to be in the ltsp.conf file for the dhcp-boot: value.
Hmmm, made the change and still the same result.
restart the service:
[code]sudo ufw disable
sudo service tftpd-hpa restart[/code]
Here is what my /var/log/syslog file reports for that last boot attempt.
[url=“/_imported_xf_attachments/0/654_var log syslog.jpg?:”]var log syslog.jpg[/url]
you are using eth1 not eth0… these are very important pieces of information to include. are you actually using eth1? If so you need to edit your default file to reflect that information, try net1 in place of net0, if not an error has been made and I would re-configure the server again
Yes this is correct I am using eth1. I have been looking through all this for so long and it never dawned on me that this would need to be changed in the default file. I definitely do not pretend to be an expert on linux and its various functions, but have been able to poke by so far.
Seems like i may have other issues going on. On boot the tftpd-hpa service is running but when i try to restart the service it hangs. When I get the status of the service it comes back as tftpd-hpa start/killed. Also after running ufw disable, the command completed successfully however upon a system reboot the firewall service is again active.
make sure you didn’t set DNSMasq to be the tftp server in the conf settings.
sudo apt-get purge ufw
Usually the disable command stops the Firewall from running, if it is still running after you have disabled it, that will get rid of the firewall for you.
also why are you restarting the tftp service? you need to restart dnsmasq.
TFTP Is not enabled in the dnsmasq.conf or ltsp.conf. I think at this point I may reconfigure the machine. I did create a clone of the drive before installing fog so that i could roll back. Would you recommend that I just use eth0 to make the setup more straightforward?
Thank you both for your assistance.
[quote=“Tom Elliott, post: 25142, member: 7271”]restart the service:
[code]sudo ufw disable
sudo service tftpd-hpa restart[/code][/quote]
I was restarting as per this post by Tom. I will remove the firewall and try again.
It doesn’t matter which NIC you use but you need to be consistent, I have only ever used one NIC so I am not much help in setting up or configuring the other NIC but it can’t be too difficult, just remembering to supply the new NIC information anytime you run across one mentioning the OLD NIC.
If I remember correctly someone raid bonded two NIC and was getting some insane speeds… Maybe I should look into this…
[quote=“Paul Freeman, post: 25150, member: 23545”]I was restarting as per this post by Tom. I will remove the firewall and try again.[/quote]
ahh, I see, sorry I missed his post that makes sense now haha
Well after purging UFW and a reboot i get something slightly different when trying to boot a client. Rather than immediately stopping at the TFTP boot sequence the HP8300 pauses there for a minute as though its trying to connect. Though still does not connect…
The HP8000 still gives the same error.
I set up a new fog server on my linksys router last night and ran into the same issue, I am going to look over my configurations when I get back to my working box this afternoon and make sure everything is in it’s place.
The only major trick to running dual nic’s is when you set the one FOG will use for imaging to static for whatever network it will be using you need to leave off the default gateway on it or you will lose all internet connectivity(Assuming the network used is not connected to your actual network), if it is connected to your actual network then you should not be using a second NIC in the first place.
I Just tried my set up on my switch and the settings in the walk through work. The only thing I noticed is I forgot to tell you where to put the tftpboot and the pxelinux.cfg.
First make sure your default file is in the correct location. open your command prompt and type
It will display a list of the files and directories in the folder tftpboot.
There should be a folder named pxelinux.cfg if not, create it, and make it readable. If it’s already there apply the chmod command below to make it readable.
sudo mkdir pxelinux.cfg
sudo chmod 0755 pxelinux.cfg
Now navigate into the folder and create the default file we spoke of above, I don’t have any linksys routers here, or I would try the set up now. I can try again when I get home, but I have this working on my production environment. As long as these settings are correct it should work, unless we have some hoops to jump through to get it working on linksys.
For now, check the settings, the default file, and the folders and try to boot again. If I fails, try setting up a different machine and use only one NIC and run through the settings again.
Actually, what I have found, is my machine still had a lingering pxelinux.0 and it was using that to boot with.
I am attempting to get dnsmasq to work with undionly.kpxe and I am not having much luck.