Bypass DHCP completly?
-
I am still a newb to fog and linux so please forgive me if these are basic questions.I have a couple of problems. First, if I am remembering right, I believe there was an option to make the fog server bypass a dhcp server during install. Right now, I need to bypass our network dhcp and have machines connect directly to the fog server to be imaged. Was I imagining this option? If not how can I set the fog server to do this if it’s set to utilize our DHCP server right now?
Second problem, how do I change my server name so when install the client I do not have to type what the server is called now and just use the default setting that is in the client?
Thank you.
-
@xburnerx00 said in Bypass DHCP completly?:
Right now, I need to bypass our network dhcp and have machines connect directly to the fog server to be imaged.
What exactly do you mean when you say bypass? Please give us more details.
Second problem, how do I change my server name so when install the client I do not have to type what the server is called now and just use the default setting that is in the client?
To change the server name on a modern Linux systems you’d use the
hostnamectlcommand. But I am fairly sure this is not what you want in the first place. If I get you right here you mean the namefogserverthat is used by the fog-client installer by default. You’d need to add this name to your internal DNS server to make this work. It’s not enough to just set this name using the mentionedhostnamectlcommand.Maybe you want to check out the command line options of the installer: https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_0.10.0.2B_Installation_Options
-
Forgive my ignorance, but I thought during the initial setup of fog, there was an option that if a person was not able to have access to the dhcp server then they could configure fog to not use a dhcp server. I guess fog would be setup to act as its own dhcp? I am not sure, I may be thinking of something else.
As for the server name change, I will have to look more into those options.
-
@xburnerx00 You are right. The FOG installer asks you if you have your own DHCP server that you can change to do PXE for you or if FOG should install and act as DHCP server itself.
So do I get your question right? You installed FOG without DHCP and now want to change that and make FOG do the DHCP thing for you? Before I give you more details on this I hope you understand that you should never ever have two DHCP servers within the same network subnet. If you do have one already and want the FOG server to do this for you now I highly recommend you completely shut down the existing DHCP server because it will cause you a lot of trouble if you don’t!!
Beside complete moving DHCP (and with that PXE) to your FOG server there is another route you can go. There is something called ProxyDHCP where you have an existing DHCP server that only hands out the IP information to the clients. Beside that you can install dnsmasq software on your FOG server that does the ProxyDHCP for you which essentially just adds the PXE boot information. See some details on this here: https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server
If you really want to shut down your other DHCP server and let FOG do this for you then let me know and I will tell you the details. But I have a feeling that this is not what you want.
-
The ProxyDHCP option seems to fit what I am looking for. I need to leave the current DHCP server running and I can not touch that. In the instructions for ProxyDHCP, it says not to set DHCP address or DNS and not set FOG as a DHCP. I have already set up FOG, months ago, to use our current DHCP, the question is how do I clear the settings in FOG before I start setting up ProxyDHCP?
-
@xburnerx00 said in Bypass DHCP completly?:
I have already set up FOG, months ago, to use our current DHCP, the question is how do I clear the settings in FOG before I start setting up ProxyDHCP?
Can’t follow you here. If you had things running with an external DHCP server there is nothing that was set within FOG. Understand it’s not FOG calling out to your external DHCP server to use it. When clients boot up they ask for an IP and PXE information (if enabled so in the BIOS) to boot from network. If that PXE information is not provided by FOG but your existing DHCP server then you need to change the settings of this DHCP server back to not hand out PXE infos (DHCP option 66 & 67).
-
Ok, I understand. Then it seems like I can continue with setting up ProxyDHCP.
Thanks for the info and clearing it up for me.
-
@xburnerx00 I have a tutorial on how to setup dnsmasq on the FOG server. If you follow my guide it should take about 10 minutes total to setup dnsmasq and have it operational. https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server
-
@george1421 Can confirm, had to switch to ProxyDHCP after the ISP upgraded the modem that has a buggy DHCP implementation (turning off DHCP makes it not give out IPs but the DHCP server is still running so it just NACKs all the IPs lol)
