Fog affecting internet on network
-
Hi Tom, thank you for your quick response
Yes, the tutorial that I followed did say to install the DHCP server with Fog. I did wonder whether it was to do with this too, but seeing as it has only started affecting our work network after roughly 1 year of it being installed I was slightly confused.
So, this might be a silly question -If I reinstall Fog now and select “no” during the installation when it asks about the DHCP server, will I have to manually put one in for hosts when doing the “Full Host Registration and Inventory”, or will it just be allocated one from our router instead?
Thanks again
-
They’ll be allocated one from your router, which is likely what’s causing the problem in general.
Basically, you have two DHCP server’s on the system which would give you the problems you’re describing. Why this suddenly started occurring is beyond me too. All I can guess is your regular DHCP server is handing out IP’s within the range of the FOG Server’s scope now, where before it wasn’t.
To fix, all you should have to do is uninstall dhcp server from the server itself. You can upgrade if you want, but I don’t know if it’s going to fix the dhcp problem.
-
Thanks again for your reply Tom,
Looking back at it now, it does seem pretty obvious about the DHCP server and that I should have selected “no” during the installation. This is what you get for blindly following a tutorial without concentrating fully on what it was asking me to do.
OK, so my solution for this would have been to backup my image files and format/reinstall the Fog server and selecting “no” to the DHCP during the install, but you mention uninstalling the DHCP server instead. How would I go about doing this? Can I do it though the Fog dashboard interface, or will I have to go through the Ubuntu Terminal using sudo commands etc?
I am most appreciative of your time and information so far Tom, so if I have just opened up a can of worms asking how to uninstall Fogs DHCP please just tell me and I will just go through format/reinstall route instead - I honestly don’t mind.
Thanks again
-
You will have to open a terminal and run a few sudo commands, though I don’t know which ones specifically.
something like:
[code]sudo apt-get remove --purge isc-dhcp-server dhcp3[/code] -
Hi Tom,
Thank you for the sudo command, you were very close too! I found that you had to add “-server” to the end of it, so in full it was -
sudo apt-get remove --purge isc-dhcp-server dhcp3-server
This seems to have done something, as my Fog server at home never used to be able to get internet access and now it works!
The only issue now, is that when I try to PXE boot a machine I get the “no boot filename not received” error. I get the feeling that Fog is still trying to use it’s own DHCP server which is now not there anymore, so it is timing out and giving that error message.I could be completely wrong though…
-
I think it’s more related to your Option 66/67 settings on the network.
As you’ve removed the dhcp server that was handing over this information, it no longer exists as you stated.
Seeing as you have a primary DHCP server, you need to set that main system to know where to get the files needed to PXE boot.
-
Hi Tom,
Thank you again for your response. Your advice is very appreciated but unfortunately my network skills/knowledge have hit a brick wall, and although I have read into what you have suggested I still can’t seem to get my head around it
Setting my main DHCP server (which is my router) to know where to get the PXE boot files, I imagine is either logging into my router and doing something in there, or using Ubuntu to tell my router where to look for the PXE boot files (presumably the Fog server IP address).I may not be making much sense here so how about this -
If I back up my image files now and decide to upgrade to a more up to date Fog version, can I choose “no” for the DHCP server on Fog, and my main DHCP will be configured automatically? (I have a feeling this is wishful thinking).
Am I right in thinking it’s better to go for an earlier version than 1.2.0. as this is still a “work in progress”?
Many thanks
-
You can do one of two things at this point. Yes, you can back up your images and install a fresh server, or you can try using DNSMASQ to get your current server working.
I recommend DNSMASQ, as this alleviates the need to edit the DHCP/DNS scope to include your fog server. and when removed your network will still run happily. This should take less than 5 minutes to set up and configure, if afterwards you are still unable to get to your boot file, a re-installation would not be a bad idea. I would still use 1.2.0 though.
Tom works quickly and diligently to fix issues with 1.2.0, and upgrading is a piece of cake when an update is available
-
Hi Jaymes, thanks for the info.
I did have a look at DNSMASQ last night when researching into what Tom had said on his previous post. Time was getting on a bit, and just reading the word DHCP was making my eyes ache so I gave up in the end. I got as far as installing DNSMASQ through the terminal and creating the ltsp.conf file, but was having difficulty getting the ltsp.conf file in the correct directory due to the permissions on Ubuntu (I have managed to successfully do this kind of thing before in Ubuntu, but time was taking its toll on me and I was starting to get restless whilst trying to figure out/remember the sudo command to do this).
I am currently at work, and life experience is telling me not to touch the work Fog server yet until I have sorted my home server out and am confident in doing it. I’ll have another look at mine tonight and update you on how I get on.
Thank you both for your time patience with me
-
That line “but was having difficulty getting the ltsp.conf file in the correct directory due to the permissions on Ubuntu” worries me.
Instead of making a file and moving it… create it and save it in the location that it belongs
[code]sudo gedit /etc/dnsmasq/ltsp.conf[/code]
Then paste in the information from the wiki, be sure to use the DNSMASQ settings for iPXE and then save the file.
This will make the file when you save and exit.
Because you use sudo, the file will be created as if it were done by the root user and issues with having to move the file should go away because the file is already in place where it needs to be. Then you need to restart the dnsmasq service and edit your /etc/exports file as the wiki commands, set up the symbolic link and all should be well.
-
Well I promised an update so here it is.
Unfortunately after following your precise instructions and steps from the wiki you linked me, it is still giving me the same grief
I think it’s time to give up trying to fix this issue and just do a reinstall.
Many thanks to you both for your time and help, it is much appreciated!
Kind regards
Harrison -
[quote=“Haz, post: 39698, member: 3272”]Well I promised an update so here it is.
Unfortunately after following your precise instructions and steps from the wiki you linked me, it is still giving me the same grief
I think it’s time to give up trying to fix this issue and just do a reinstall.
Many thanks to you both for your time and help, it is much appreciated!
Kind regards
Harrison[/quote]If you would like help with your DNSMASQ just send me a pm we can work together to solve the issues
