Fresh Install of Fog - Setup PXE Boot
-
I have a fresh install of Fog. The desktop it’s running on is NOT connected to the internet at this time. I have a switch plugged into the computer and a laptop I’m using to test PXE. The FOG’s IP address is the internet 127.0.0.1. PXE boot is not working.
Where do I troubleshoot or what needs configuring?
Thanks,
Damian -
Hi,
you have to set dhcp option 66 and 67, have you read the wiki?
Regards X23
-
Lets get a bit more information here.
- What version of FOG are you using?
- What device is providing your dhcp services?
- From your fog server, please run and post the output of this command.
ip addr show
-
This post is deleted! -
@george1421
Version is 1.5.0
I want the FOG server to handle DHCP (It will not be connected to our companies main network)
The IP it has right now is 127.0.0.1 -
@dpotesta50 said in Fresh Install of Fog - Setup PXE Boot:
The IP it has right now is 127.0.0.1
This is A or THE problem. 127.0.0.1 is a loop back address for a pseudo network adapter. You must give the FOG server a real IP address for your imaging network then reinstall FOG. The FOG services don’t like it when you change the IP address of the FOG server after FOG is installed.
As a side note, you can setup the fog server with 2 network interfaces. One will be for remote system management and the other one will be for a dedicated imaging network. Either way 127.0.0.1 is the wrong answer.
-
@george1421 Good info. I’ll reload it now. So after this is there still more configuring for PXE or is part of the installation?
-
@dpotesta50 If you are using the FOG installer, then it should setup everything for you. Once you have fog-reinstalled we can look to see if your services are configured correctly.
-
@george1421 I wasn’t getting passed the “create repository” part of the installation so I’m just reinstalling Ubuntu then FOG.
Your last part about using two interfaces. I’d like to be able to setup wifi for internet access, and ethernet for the imaging but I need to make sure the DHCP services on FOG don’t wreak having on our Microsoft network.
-
@dpotesta50 OK once you get unbuntu reinstalled. Setup eth0 (or what ever your ethernet adapter is) on your imaging network. Do not give it a gateway address since its on an isolated network. Give it an IP address unique to your imaging network.
Then connect your second network adapter (wifi in this case) to your business network and give it a default gateway so the fog installer has internet access. Its only needed during installation to download the latest kernels. Post install you will use it for FOG administration if needed.
Now when you install FOG only bind it to your ethernet interface on your dedicated imaging network. FOG will not connect to wifi unless you tell it. Once FOG is installed if you want to double check to make sure it didn’t bind to the wireless interface we can look at the isc-dhcp config file.
But in general, if you don’t tell fog about your wifi interface it will not use it.
FWIW, FOG works perfectly well using a ms windows dhcp server too.
-
@george1421 on the part of the installation that asks if I want to change the default network interface. How do I know which it’s default to?
-
@george1421 or to change gears, can I just set it up to where I don’t need Fog to act as a DHCP server, keeping it nice and simple? Will the PXE client’s get their IP addresses from Microsoft via the FOG server that way?
-
@dpotesta50 There is no real simple. For the clients to get their dhcp addresses from your business network you will need to have a router setup to pass the dhcp requests to your dhcp server.
Lets take a step back, why do you feel you need a dedicated imaging network?
-
@george1421 The main concern was keeping the FOG DHCP from interfering with the corporate MS DHCP.
-
@dpotesta50 So if your clients use MS dhcp server then there is no reason to have a dedicated imaging network (understand there ARE reasons to have a dedicated imaging network, I just want to see if your use case fits).
You do not need to use fog dhcp server at all. It is provided when your needs are specific. As long as you can configure dhcp options 66 and 67 in your MS dhcp server then you are good to go. If you have a mix of uefi and bios (legacy mode) computers you will need a windows 2012 or newer dhcp server to create the filters to dynamically switch between the boot files. This isn’t a requirement, but it makes life easier for you.
-
@george1421 well since I’m not over the main network and those who are, are busy with other projects lets keep FOG handling the DHCP for the PXE clients.
-
@dpotesta50 said in Fresh Install of Fog - Setup PXE Boot:
on the part of the installation that asks if I want to change the default network interface. How do I know which it’s default to?
OK then back to where you were.
The default network adapter will be your imaging network adapter. You can view this by the following command on the fog server linux command prompt
ip addr showThat will show you all network interfaces. The one with teh IP address that matches your imaging network is the one you want to set as your default. It may be named eth0 or something else based on your linux distro. -
-
@dpotesta50 enp2s0 is your wired ethernet adapter and should be your FOG default adapter. But your don’t have an IP address range assigned just yet. Don’t install FOG.
It looks like your wireless interface is connected to 192.168.50.x network. Is that right?
-
@george1421 Wiresless is getting DHCP from MS. Based on what you instruction I need to bind Fog to the ethernet which I gave a static 192.168.100.100.
