how to setup FOG server on Isolated netowork
-
How can I isolated my fog server from the internet without changing my setting on the fog server?
-
What version of FOG?
-
I just updated my fog server yesterday I’m not sure of the version. I can take a look when I get home.
-
@cnbgeren Just for clarity, you don’t want your fog server to reach out to the internet, correct? But you don’t want to change any of the settings in FOG?
The easiest way to do this is to just remove the default route from your network interface. This way your FOG server will only know about your local LAN and have no where to send data not destined for your local LAN. You will be restricted to only being able to communicate with devices on your local subnet.
-
@Wayne-Workman
Running Version 1.3.0-RC-5 -
it looks like my FOG server took over as my local DHCP server which caused all kinds of issues with my home PC. Had to unplugged the FOG server and reboot my router to fix the issue. would your suggestion keep this from happening? Also i’m not sure I understand you about the default route part. Sorry for the dumb questions and now i can’t PXE boot to the server but I can HTTP to server using the laptop with the PXE boot issue.
-
@cnbgeren I’m just trying to understand your logic for not wanting Internet access with your fog server.
In your case where you have a home router that is handing out dhcp addresses, but you want to run FOG on the same network and your home router as your dhcp server you can use a linux service called dnsmasq. This is a proxy dhcp server that will supply the missing information to a standard dhcp request.
@Wayne-Workman just created an updated document (that I can’t seem to find for setting up dnsmasq) Here is my older one that might get you started. https://forums.fogproject.org/topic/6376/install-dnsmasq-on-centos-7
-
Let me ask you one more question, it may even sound a little stupid, but if I take the Fog Server and plug it up to a hub then take the laptop I’m trying to PXE boot and plug it up to the hub also, without any internet going to the hub should it still be able to PXE boot?
-
@george1421 said in how to setup FOG server on Isolated netowork:
@Wayne-Workman just created an updated document (that I can’t seem to find for setting up dnsmasq)
It’s still in the works. I think I’m overthinking the article. To me it’s easy to setup because I’ve done it several times. https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_/dnsmasq-_DRAFT
The new snapinpacks article will get completed before this.
-
@cnbgeren said in how to setup FOG server on Isolated netowork:
Let me ask you one more question, it may even sound a little stupid, but if I take the Fog Server and plug it up to a hub then take the laptop I’m trying to PXE boot and plug it up to the hub also, without any internet going to the hub should it still be able to PXE boot?
In case, your FOG server will need to supply dhcp and dns services in addition to the standard FOG feature sets. You will also need to have a management computer on this mini network if you want to interact with the FOG server directly.
-
all I need the fog server to do is upload an image and down an image using PXE boot. Can I get by without DNS and DHCP?
-
@cnbgeren For imaging you don’t need dns if you reference everything by IP address. FOG uses (internally) IP addresses only so you are good there.
dhcp is mandatory, the target computer uses dhcp to acquire its IP address as well as PXE boot information. You can use a home router if you are able to set dhcp options 66 {next-server} and 67 {boot file}. If your home router does not support this you can install a service into your fog server called dnsmasq that will provide the information your home router can’t. But in your case you will be on an isolated LAN so you will need to install the dhcp service into your fog server. This is pretty easy since the fog installer asks you if you want to do this during install time.
So to recap, dns no. dhcp with pxe support, yes.
-
ok thanks, During the install of FOG software I took the defaults so DNS and DHCP were installed. for some reason, the FOG server worked perfectly over the weekend but now I’m not able to PXE boot to the server and
I’m not to able to ping www.google.com but I can ping 8.8.8.8 so I guess this is a DNS issue. here the error message on the server . do you think removing DNS could fix the error message below
-
@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?