Isolated Network Install - No Internet
-
I have been searching around and it seems you need internet during the initial set up. https://wiki.fogproject.org/wiki/index.php?title=FOG_on_an_Isolated_Network
I am constrained as I cannot connect this computer lab to the internet at all, I can move files to this standalone network. I have access to a YUM mirror and have been following the redhat install guide. I am able to get through most of the install but break at “Downloading Kernal, init and fog-client libraries … Could not download init.xz properly.”
Any chance of installing on a isolated network?
Thanks!
-
So this is probably frowned upon but I mirrored the git for fogproject and fos on my network. in functions.sh I replaced the web addresses accordingly, this let me ping all of the installs. I needed to comment out all of the checksum checks (sorry) but was able to get this up and running.
Apologies for implementing this way, wanted to share for completeness sake.
-
@atlas You need to have internet access to install FOG. I have seen some people install 2 network adapters in the fog server, one on the business network and one on the isolated network. The nic on the business network is for management and (install time only) internet access. This keeps the isolated network isolated.
FWIW that wiki page you referenced is 10 years old and does not currently apply to a current version of FOG.
FWIW: You can manually download the inits and kernels from here: https://github.com/FOGProject/fos/releases/
-
@george1421 Thank you, will move over the kernels and inits and see if I can get something to kind of work before bringing up a 2 network adapter solution.
-
So this is probably frowned upon but I mirrored the git for fogproject and fos on my network. in functions.sh I replaced the web addresses accordingly, this let me ping all of the installs. I needed to comment out all of the checksum checks (sorry) but was able to get this up and running.
Apologies for implementing this way, wanted to share for completeness sake.
-
[[undefined-on, A atlas, ]]
-
@atlas When it comes to opensource, the only wrong answer is one that doesn’t work. Well done!
Another hackish way would be to instead of changing the programming, you could enter a fake/but valid entry in the /etc/hosts table to point the dns entry to your internal server. This way you can use fog native code when version next comes out. But again if it worked for you it was the right answer.
