Newbe Fog installation issue

[Sebastian Roth]

@Wayne-Workman said in Newbe Fog installation issue:

I didn’t add any repositories to my 18.04 server.

Maybe this has changed from 18.04 to 18.04.1??? Just a wild guess. Not sure if I am keen to try out. Not sure if there is anything in the setup causing that repository section to be added?!

@mstumpo Sorry we rumble on about such things in your topic. Stopping it now!

[danuel]

For UBuntu 18.4.01 LTS + fogproject-1.5.4
Try Run this:

sudo echo "deb http://cz.archive.ubuntu.com/ubuntu bionic main universe" >> /etc/apt/sources.list
sudo apt-get update
sudo apt-get upgrade
sudo tar -xzvf fogproject-1.5.4.tar.gz
sudo cd fogproject-1.5.4/bin
sudo chmod 777 installfog,sh
sudo ./installfog.sh

Now you are able to installation

[mstumpo]

OK, got Fog installed and can access the console on the local computer. However, when I attempt to PING or open the console from a remote station on the same subnet, I can’t do either. I am assuming it is a firewall issue on the local CentOS station. Not being familiar with Linux, I found the firewall dialog and enabled HTTP and TFTP, neither of which works. In addition, when booting a station to PXE, it gets an IP address, Subnet and gateway IP, but TFTP time out. Any thoughts please?

[george1421]

@mstumpo There are two prerequisites that you need to do before installing fog or you will have pains later.

1. Disable the linux firewall. For centos the command are
   systemctl disable firewalld
systemctl stop firewalld
2. Set selinux (akin to Windows UAC) to permissive. Edit the file /etc/selinux/config and change SELINUX=enforcing to SELINUX=permissive. Then reboot your fog server.

[mstumpo]

@george1421 OK, great. Thanks for the info. I’ll be there later today and will try this.

[mstumpo]

@george1421 OK, those worked and I can now open the Fog console from my laptop. I still can’t get a computer to PXE boot to Fog server. TFTP now does not show timeout, goes right to Intel Agent exiting and boots windows 7.

[george1421]

@mstumpo OK so what did you set dhcp options 66 and 67 to?

[mstumpo]

@george1421 66 - 10.0.0.164 (fogserver IP) and 67 (undionly.kpxe).

[george1421]

@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.

[mstumpo]

@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.

[george1421]

@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.kpxe I’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?

[mstumpo]

@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.

[george1421]

@mstumpo Well this is an interesting one.

1. Can you ping the fog server from the windows client?
2. 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.
3. 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:*

[mstumpo]

@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.

[george1421]

@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.

[george1421]

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.

[mstumpo]

@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?

[george1421]

@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 -la should show you the output file and pwd will 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.

[mstumpo]

@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.

[george1421]

@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.pcap

That 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.