Newbe Fog installation issue
-
@mstumpo OK so what did you set dhcp options 66 and 67 to?
-
@george1421 66 - 10.0.0.164 (fogserver IP) and 67 (undionly.kpxe).
-
@mstumpo Do you see it download (or appear to load) undionly.kpxe? You should see the fog menu if it does. Understand by default the fog menu has a very short timeout defined. So if you miss the menu, it will attempt to boot from the first hard drive.
Also be aware that undionly.kpxe is for bios based systems, you need a uefi kernel ( ipxe.efi ) if your target computer is uefi based.
-
@george1421 No, I did not. The test station is Windows 7 so the undionly.kpxe should be OK. There is no menu at all. Stations grabs IP information via PXE, TFTP line option goes by quickly and then Intel agent indicates exiting and Windows 7 boots.
-
@mstumpo said in Newbe Fog installation issue:
Intel agent indicates exiting
OK this means that its still not grabbing the file. You should see the iPXE banner as it boots.
From a windows computer, install the tftp client feature. Then from a dos command prompt key in
tftp <fog_server_ip> GET undionly.kpxeI’m only interested in if it is downloading that file or not.Also is the target pxe computer on the same subnet as the FOG server and DHCP server?
-
@george1421 OK, I ran the command. Get Error on server : Permission denied. connect request failed.
Yes, all stations, fog server, DHCP/DNS servers, etc. are on the same subnet. -
@mstumpo Well this is an interesting one.
- Can you ping the fog server from the windows client?
- You may need to temporarily drop the windows firewall to make tftp work since it functions similarly to ftp with a command channel and a data channel back.
- On the fog server key in the following
netstat -an|grep 69. You should see a line that looks like this:
udp 0 0 0.0.0.0:69 0.0.0.0:* -
@george1421 1. Yes. 2. Already disabled and 3. Just as you indicated. Also, tried PXE booting from another station. Same issue, get IP information. TFTP line immediately goes to PXE-M0F: Existing Intel Boot Agent. Selected boot device failed.
-
@mstumpo Ok lets see if we can find the bad actor here. Please follow this process: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
Upload the pcap to the forum and let me review.
-
If you can’t upload the pcap to here, then upload to a google drive and then share the link. That way you can take down the file when its not needed.
-
@george1421 The pcap has been created, but where would the default location be and how can I easily copy it to a USB drive to post here?
-
@mstumpo the file is created in the directory you were in when you ran the tcpdump command. If you still have that session open to the FOG server linux console then
ls -lashould show you the output file andpwdwill show you the path.To copy, since you are a windows person, get winscp and connect to your fog server using winscp. That will give you a windows file browser like experience to copy files.
-
@george1421 pwd shows root@fogserver. I can’t find that folder via Winscp. When I go to root via Winscp I get permissions denied. Sorry for the slow reponse but not a Linux user.
-
@mstumpo so with winscp, you logged in with the user root? if so you should be able to change to /root directory
If you can’t get it then try this from the console you ran the tcpdump command:
cp /root/output.pcap /tmp chmod 777 /tmp/output.pcapThat will copy that output file to the /tmp directory and then make it world readable. From there you should be able to pick it up with winscp in the /tmp directory.
-
@george1421 While I am doing that, is there a utility that will allow me to RDP to the fogserver (it’s a physical PC) so I don’t have to go to the server room when dealing with issues?
-
@mstumpo It depends on your OS if it has a linux gui or not. But at the very least you can get the free program called putty that will allow you to connect via a console to the FOG server.
-
@george1421 I am using Windows 10 and was looking for a way to work like I would on a Windows server using whatever variant of Remote Desktop would work to connect to a Linux box. Putty is good for some command line things, but I like being lazy…
-
@george1421 Here is the pcap file. Let me know when you have it so I can delete it from my end. https://www.dropbox.com/s/id6b7r5tscboni0/output.pcap?dl=0
-
@mstumpo Look at the forum chat bubble in the upper right corner for a few more questions.
-
The root of the issue was the OP missed both prerequisites (disable firewall and set selinux to permissive). Once that was done he was able to get the iPXE menu to appear.
