how to setup FOG server on Isolated netowork

[Wayne Workman]

@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.

[george1421]

@cnbgeren said in how to setup FOG server on Isolated netowork:

@george1421

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.

[cnbgeren]

@george1421

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?

[george1421]

@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.

[cnbgeren]

@george1421

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

[Sebastian Roth]

@cnbgeren Please post the contents of /etc/resolv.conf and/or /etc/NetworkManager/NetworkManager.conf

[george1421]

@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.

[cnbgeren]

@george1421

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.

[george1421]

@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.8

or
dns1=8.8.8.8

[cnbgeren]

@george1421

ok will do as soon I get home. would the command to retrieve the information be sudo or cat /etc/resolv.conf file?

[george1421]

@cnbgeren cat since you are only listing the file

[cnbgeren]

@george1421

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?

[george1421]

@cnbgeren If dhcp is setup correctly and offering the required PXE information then, yes it should.

[cnbgeren]

@george1421

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

[george1421]

@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)

[george1421]

@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.

[cnbgeren]

@george1421
I’m sorry I don’t understand what your asking

[george1421]

@cnbgeren said in how to setup FOG server on Isolated netowork:

@george1421
I’m sorry I don’t understand what your asking

You 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.1 to something like nameserver 8.8.8.8 save 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.

[cnbgeren]

@george1421

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

[george1421]

@cnbgeren Your fog server has a staticly defined IP address right??