Fresh Install of Fog - Setup PXE Boot
-
This is really frustrating. Once I get wifi back up, FOG wants to bind to that NIC as it’s main. I don’t know the terminology it’s looking for when it asks if I want to change the default network adapter. If I say yes and enter the NIC’s name, it throws syntax error.
-
Got it!
Kinda dumb, change to adapter number “2”. -
Got to the end of the installation where it updates the database schema. Site won’t open in Firefox. Just times out.
192.168.100.100/fog/management -
@dpotesta50 Did you remember to disable the ubuntu firewall and set the selinux permissions to permissive as recommended in the prerequisites?
-
@dpotesta50 said in Fresh Install of Fog - Setup PXE Boot:
192.168.100.100/fog/management
This will only work if you are on the imaging network, to access the managment interface from the business side you will need to find the IP address of the wifi adapter.
-
@george1421 I’m running on Ubuntu desktop, is this still required? (selinux permissions)
-
@dpotesta50 (sorry I’m a rhel guy) I’m not sure if ubuntu has selinux enabled or not by default. If its on, then its mandatory that you set it to permissive. If from the linux command prompt you key in
cat /etc/selinux/configlook for a line that saysSELINUX=permissiveorSELINUX=disabledIf that is set then selinux will not cause you pain. If its set to enforcing then you need to change it as root and reboot. -
@george1421 It shows "SELinux status: Disabled
-
@dpotesta50 Ok so then selinux will not be in your way. Did you ensure that the firewall has been disabled? I know that IS on by default for ubuntu.
-
@george1421 Yes I ran “sudo ufw disable”
-
@dpotesta50 So if you run
ip addr showto get the IP address of the wireless interface and then from the business network attempt to connect to that ip addresss/fog? -
@george1421 The dashboard is up and running. I can access it and all the options. I just tried to PXE boot a laptop to it, no server found.
-
@dpotesta50 It’s very very slow though. Changing from option to option within the FOG program takes a minute or so.
-
@dpotesta50 Ok the slowness is from both networks?
OK, now lets work on one issue at a time.
So fog is the dhcp server, we need to make sure that isc-dhcp service is running on the fog server. Run this
ps aux|grep dhcpand/or you can check to see if its listeningnetstat -an|grep 67The fog installer should setup the isc-dhcp config file to look like this: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_1
-
-
@dpotesta50 well that explains why no dhcp boot. Its not running.
First lets try to start it. This might be the command
systemctl start isc-dhcp-serverSee if that gives you a positive.When you run the netstat command you should see something that looks like this
udp 0 0.0.0.0:67If that works then you will want to run this command
systemctl enable isc-dhcp-serverto enable the server to start at each reboot. -
@george1421
That list is so long I have to roll the scroll wheel about a dozen times to get to the bottom. -
I remoted in with teamviewer and helped the OP get things working correctly. We had to ensure that the dhcp server only bound to the imaging lan NIC adapter and not both. We also found a nuance with ubuntu where it only wanted one interface up at a time by default. Once we had both interfaces up, fog installed correctly and like the OP needed it. Solving this case.
