Questions about FOG on isolated network
-
https://wiki.fogproject.org/wiki/index.php/FOG_on_an_Isolated_Network
What is the IP address to be used by this FOG Server? [current address]192.168.1.1
Your server’s current Internet address is displayed. When FOG is installed we will be disconnecting from the Internet and defining our own private IP address. Enter your future static IP private address: 192.168.1.1So 192.168.1.1 is on a network with internet access? At what point is the address changed to be on the isolated subnet? What config file is edited to do this? With this setup, the management page will be on 192.168.1.1/fog/management, this is not good. It must be on the isolated subnet and I don’t know where to change this after it’s already been set up.
Would you like to use the FOG server for dhcp service? [Y/n] Y
Yes. This allows clients to get IP addresses on our private network and connect to the FOG server.Where is this set up? Will the FOG installer do it automatically? Or do I have to set up DHCP independently?
Basically, due to requirements in the workplace, the imaging solution cannot touch the production network. FOG will be on 10.0.1.0 /24 with a switch and the clients to be imaged. There will be no DHCP server, or anything else, so the Linux box must do everything.
-
@mageta52 What Linux distrubtion will you be using?
FOG simply reads the IP information from your current interface IP, if you want to change that you have to change your static IP. (how will depend on your linux distribution)
You fill in your future static subnet IP at the step it asks you to do so.
Then you install FOG which will use that IP for everything. After it’s installed you can then change your interface IP and move FOG to the isolated subnet.
FOG will automatically generate a DHCP config and start the DHCP server service. Since you’re on an isolated subnet, the DNS won’t matter, nor will your gateway.
-
@Quazz Excellent, I’ll try this. Using Fedora workstation 23 by the way.
-
Without a specific question, then answer is Yes.
You can run a FOG server on an isolated network. Your FOG server (or some other device) must supply dhcp and dns services. Beyond that FOG will supply the remainder of what is needed for imaging. The main key point is that you set a static IP address for the FOG server before you install FOG. Beyond dhcp and dns (both could be supplied by the fog server) FOG is pretty much standalone.
-
@george1421 Why is it important to set the static IP before installing FOG? I’m still confused about this.
- Internet access is needed to get the FOG files to install, so initially I must be on a subnet that has a gateway to the internet, in my case it’s 192.168.1.0.
- The isolated network I’ll use is going to be 10.0.1.0 /24. If I set my interface to something like 10.0.1.1 I won’t have internet access and cannot even begin to install FOG
- It sounds like what Quazz is saying, is that I can be on the local subnet ( 192.168.1.0 ) get the install done, then statically set the interface to 10.0.1.1 or something else on that isolated subnet, and then FOG will be able to adjust to it accordingly. Is this correct?
-
@mageta52 You’re overcomplicating it. Set a static address for the fog server prior to installation. When you put it on an isolated network after installation, it will retain that IP, it will continue using that IP - and your isolated network will use the same subnet mask and range as the one it was on prior.
FOG sets a ton of settings based on the IP - it’s written in many, many places during the installation. While it’s possible to change all these (and I’ve done it before), I wouldn’t recommend it to the newcomer.
-
@Wayne-Workman You’re right, I wasn’t thinking the whole scenario through. I get it now.
After updates are finished I’ll move on with the install and report any issues I run into.
-
@mageta52 Sorry for the delay, Wayne answered how I would have.
As for your deployments. I understand you need a dedicated deployment network. But if its possible, you can install a second nic card in your fog server (once fog is installed) and connect it to your business network for image deployment only. FOG will continue to use the isolated network for deployment and the 2nd nic for management from your business network.
-
@mageta52 said in Questions about FOG on isolated network:
- It sounds like what Quazz is saying, is that I can be on the local subnet ( 192.168.1.0 ) get the install done, then statically set the interface to 10.0.1.1 or something else on that isolated subnet, and then FOG will be able to adjust to it accordingly. Is this correct?
You can connect the fog server to the business network to download FOG 1.2.0 stable then switch the network interface to the installation LAN and install FOG. For the trunk build you will need to have internet access (with a second nic) but initially fog must be installed with the main ethernet adapter at the final IP address and subnet mask.
-
This post is deleted!
