Cant pxe boot to fog.
-
@blindcat420 said in Cant pxe boot to fog.:
When I try to pxe boot from a laptop with legacy booting it fails and gives me pxe-e53 no boot filename received.
@Wayne-Workman You are right the next steps is to grab a pcap of the external laptop pxe booting. That pxe-e53 error is telling. The soho routers will typically post themselves as the next server with no boot file.
@blindcat420 Follow the instructions here and post the results in this thread: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
-
I installed tcpdump and have created the output.pcap file. I dont have much experience with linux hence why I’m messing with it.
How can I move that file to one of my windows file shares? So i can upload it here?
Answers to earlier questions.
I have a few vm’s 1 uses legacy, 1 uses uefi, i have a laptop that is currently set to legacy but i can change it to uefi.
I just installed dnsmasq the other day so it would be whatever the latest version is.
-
-
So I got a update. Seems I’m getting more action after disabling the firewall on fog.
vm 1 with legacy boot gives me this now.
vm 2 with uefi boot gives me this.
the laptop gives me the same error as the first picture.
-
@blindcat420 Just a quick question. Did you disable selinux? Check with
sestatusor withgetenforce. This is in the CentOS 7 instructions. -
@blindcat420 Ok those screen shots are very helpful in telling where its going sideways. Can you grab another pcap now that you have the linux server firewall disabled. In the previous pcap I only see dhcp “Offers” from your firewall/router and not dnsmasq.
I also suggest that you load wireshark onto a windows computer so you can review the pcap file.
Remember a dhcp/pxe boot process always follows this flow.
Client ->Discover
DHCP Server->Offer
(if you have proxyDHCP) DHCP Proxy ->Offer
Client ->Request
DHCP Server ->ACK
(end of normal dhcp)
(start of pxe booting)
Client ->DHCP Proxy
Client ->DHCP Proxy
Client ->tftp server (request file size)
Client ->tftp server (request file)Also if you want to interact with FOG server from windows land you will need 2 applications in your tool box.
- Putty (remote ssh termial)
- WinSCP (remote file copy explorer)
From your picture, just for clarity 192.168.1.3 is your FOG server?
From the pictures it appears that dnsmask is working but maybe the tftp server is sending the file. The pcap will tell us a bit more where to look.
-
@george1421 Very strange I think. The pcap was captured on the FOG server I suppose. Why don’t we see any packets from dnsmasq??
@blindcat420 Ok let’s check if your TFTP server is running properly. Run
ps aux|grep tftpandnetstat -antup|grep 69, and post the full output here. -
@Wayne-Workman said in Cant pxe boot to fog.:
sestatus
i disabled firewalld i assume that is different than selinux?
-
-
192.168.1.3 is the fog server.
for output.pcap i did run that from the fog server and it was before i disabled firewalld.
output2.pcap is after disabling firewalld.
this is what i get with those two commands.
-
@blindcat420 said in Cant pxe boot to fog.:
i disabled firewalld i assume that is different than selinux?
You need to set SELinux either to permissive or disabled, instructions for that are in the CentOS 7 tutorial.
-
@blindcat420 Ok then, TFTP is not running. Usually FOG sets it up properly when running the installer. As you are running CentOS tftp is provided by xinetd. So please run the following commands:
systemctl start xinetd systemctl status xinetd@Wayne-Workman SELinux is disabled already, see posts further down.
-
So i started xinetd.
Iooks like i get the same error as before. so seems something is wrong with tftp
-
@blindcat420 can you run a simple tftp transfer test? First can you double check rpcbind is running? Usually, I see tftp in a call port created when requested rather than a constant seeing of port 69 being open. This is usually handled by rpcbind utility. Xinetd May play a role as well but I don’t know if it running alone will prove anything.
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP#Testing_TFTP
-
-
@blindcat420 In the xinetd status picture I see
... removing tftpand so I guess something went wrong with the configuration file. Please check/etc/xinetd.d/tftpand post the full content here. The FOG installer does manipulate that file but I have not seen something going wrong here in the last couple of months or even years. -
-
@Sebastian-Roth said in Cant pxe boot to fog.:
/etc/xinetd.d/tftp…
Here we go. Your config hasn’t been modified by the installer. Maybe the installer didn’t run all the way to the end? When it asked you to access the web interface, did it proceed further after you hit ENTER there? You can simply fix the path in the config (should be
server_args = -s /tftpbootanddisable = no) and restart xinetd but you might run into other issues if the installer hasn’t finished last time. The food thing is you can simply re-run the installer to do it’s thing again. It will detect that all packages are already installed and do all the config stuff for you again. -
I will give that a try. I dont really remember. As far as I know the install should have completed. When I try to run this command from that tftp troubleshooting page. I get this.
Doesn’t look like i have a folder called tftpboot.
When you say rerun the installer are you talking about fog?
-
@blindcat420 said in Cant pxe boot to fog.:
When you say rerun the installer are you talking about fog?
Yes, simply do as if you’d do your FOG install normally. Answer the questions as you did last time and let it run through. I am fairly sure the installer didn’t finish last time as it would have created
/tftpbootand copied the iPXE binaries to it - and many more things.
