how to setup FOG server on Isolated netowork
-
@cnbgeren Please post the contents of
/etc/resolv.confand/or/etc/NetworkManager/NetworkManager.conf -
@cnbgeren Just for clarity, you have a fog server plugged into an isolated switch with only the target connected? If so then your fog server can not pull any updates or deployment status messages from the FOG Project web site. You will get the screen shot below. That is OK, message on an isolated network.
-
it’s not plugged up to isolated internet yet. Right now its plugged up to my router. everything was working fine until yesterday. then my another PC started using my FOG server as its DHCP server which caused all kinds of issue with my home network. Once I rebooted my router my issue was resolved with my home PC but now I can’t PXE boot to the FOG server or access the internet. I can ping 8.8.8.8 but can’t ping www.google.com any help would be great.
-
@cnbgeren From your fog server you can’t ping www.google.com? If that is the case then please follow Sebastian’s recommendation to post the results of /etc/resolv.conf file. That file tells the fog server where to get dns information. If that is blank then you will need to add one line of text to that file.
Depending on your host OS you need to add this line if one exist
nameserver 8.88.8or
dns1=8.8.8.8 -
ok will do as soon I get home. would the command to retrieve the information be sudo or cat /etc/resolv.conf file?
-
@cnbgeren cat since you are only listing the file
-
if I could ask another question. If the FOG server is running DHCP and is plugged up to a switch without internet access, I should be able to PXE using a laptop plugged up the same switch?
-
@cnbgeren If dhcp is setup correctly and offering the required PXE information then, yes it should.
-
had to take a picture of the command because I could not access internet with FOG server. also could not PXE boot while connected to my router or on Isolated network using switch. thanks for your help
-
@cnbgeren simply edit that /etc/resolv.conf with vi or nano and replace 127.0.0.1 with either your ISP’s dns server or google’s {8.8.8.8)
-
@Wayne-Workman said in how to setup FOG server on Isolated netowork:
https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_/dnsmasq-_DRAFT
Where is that post you crated that documented the fedora 23 install. You had a dnsmasq section there that was pretty darn good, short and clear. You could almost dump that section into the draft link from above.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
-
@george1421
I’m sorry I don’t understand what your asking -
@cnbgeren said in how to setup FOG server on Isolated netowork:
@george1421
I’m sorry I don’t understand what your askingYou ran the cat command to show the content of /etc/resolv.conf . That content only looks up internet names from the FOG server. Probably not what you want. You need to edit that file [/etc/resolv.conf] with a text editor (anyone that linux has. Two popular command line ones are vi and nano. There may be a gui based one like gedit that is available to you.) You need to change the entry
nameserver 127.0.0.1to something likenameserver 8.8.8.8save the file and then open a command window and key in ping www.google.com. That should now reply with the IP address and a ping response. -
ok I ran the following command nano /etc/resolv.conf but now I’m getting the this message: DO NOT EDIT THIS FILE BY HAND–YOUR CHANGES WILL BE OVERWRITTEN
-
@cnbgeren Your fog server has a staticly defined IP address right??
-
@george1421 said in how to setup FOG server on Isolated netowork:
@Wayne-Workman said in how to setup FOG server on Isolated netowork:
https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_/dnsmasq-_DRAFT
Where is that post you crated that documented the fedora 23 install. You had a dnsmasq section there that was pretty darn good, short and clear. You could almost dump that section into the draft link from above.
It’s in the Fedora 21 Article. I suppose I can literally copy these optional steps to the CentOS and Fedora 23&24 articles, changing yum to dnf where needed.
-
-
@cnbgeren Yeah it looks like your dhcp server isn’t running.
Since it appears you have a unbuntu server you might want to review this document. https://help.ubuntu.com/community/isc-dhcp-server
