New to Fog + Tough scenario = Mobile FOG Server

[george1421]

Can you post a clear screen shot of the exact error you see taken with a mobile phone? The context of the error is almost as important as the error itself.

[george1421]

Beyond the error your current network should work without needing to use the fog dhcp server. Windows 2012 is fully capable to support your fog imaging as long as your target computers can get an IP address then we should be able to make the rest work.

Can you tell me what you have precisely set for dhcp options 66 {next-server} and dhcp option 67 {boot-file} on the dhcp server?

It appears your fog server and target computer are on the same subnet but I suspect your dhcp server is on a different subnet. Not an issue just adds a small bit of pain in solving your issue. Not a problem at all.

[thiagotw]

@george1421 Hi george, thank you for the fast reply.
“dhcp options 66 {next-server} and dhcp option 67 {boot-file} on the dhcp server” Where is that?

The tough scenario that I mean is, i don´t have access to the 2012 server and not even the fortigate firewall due another service provider contract, so i cannot setting anything there if i need to.

[george1421]

@thiagotw well those settings are on your dhcp server configuration.

If you don’t have access to change those settings we still have options.

The dhcp option 66 tells the target computer how to find the fog server.

Dhcp option 67 tells the target computer which boot image to load from the fog server. For bios (legacy) systems the default value for dhcp option 67 is undionly.kpxe and for uefi systems it is ipxe.efi.

Without the client receiving those values, it will not pxe boot (any imaging software that relies on pxe booting).

Can you tell me if all of the computers you would like to image are on the subnet 10.47.0.x/24

[Psycholiquid]

Did you turn off secure boot in the UEFI?

Secure boot off and Legacy boot off ins the option you want

[thiagotw]

@george1421 Can you tell me if all of the computers you would like to image are on the subnet 10.47.0.x
Yes they are…

@Psycholiquid Hmmm, i will take a look into this, thx.

[george1421]

@thiagotw said in New to Fog + Tough scenario :

@Psycholiquid Hmmm, i will take a look into this, thx.

You are not this far yet, but that WILL be a problem soon.

OK so they are all on the same subnet. That is a good thing if you can’t modify your existing dhcp server. There is a wiki that explains how and why you want to use dnsmasq. https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server

I’m going to take you a little different path, but in general that will be the process. For your install I want you to go ahead and install dnsmasq using your distribution’s version of dnsmasq. Once it is installed lets confirm the version that gets installed. We need version 2.76 or newer for dynamic bios/efi support.

Once you have your distributions dnsmasq installed open a linux command prompt and key in the following command, this will tell us the version number. sudo dnsmasq -v Once we have that information we will take the next steps.

[thiagotw]

@george1421 Ok, I´ts ok install through Ubuntu Software “store” ?
i got that…

Do i need to do the step from wiki? 7.Create /etc/dnsmasq.d/ltsp.conf using the following settings, modify as needed:

[george1421]

@thiagotw Well this IS confusing the dnsmasq -v says 2.75 but the installer said 2.77 (which is current). We need 2.76 or newer (2.77 if fine). If you installed it through the ubuntu store that is great, but we need 2.77

[george1421]

@thiagotw As for the ltsp.conf file, I want you to use the one listed in this post at the bottom: https://forums.fogproject.org/topic/8725/compiling-dnsmasq-2-76-if-you-need-uefi-support/6

Make sure there are no other dnsmasq config files in the dnsmasq.d directory so to mess up your setup.

Be sure to change all of the <fog_server_IP> values to the IP address of your fog server. Then restart your dnsmasq process with sudo systemctl restart dnsmasq

[thiagotw]

@george1421 I look the dnsmasq index and download the dnsmasq-2.77.tar.gz file, but how do I manually install it after unpack.

[george1421]

@thiagotw Well the post I provided with the ltsp.conf file explains how to build the file from the source image. You can do it that way (and was required before the linux distributions supported 2.76 and newer). But its better off to use your distributions dnsmasq package if its new enough. I don’t run ubuntu (rhel guy myself) so I’m a bit conflicted with what you have installed vs what your software catalog shows.

[george1421]

Just doing a quick google-fu it looks like you need to have Ubuntu 16.10 to get built in support for dnsmasq 2.76+. So it look like you will need to compile it using those instructions, sorry.

[thiagotw]

@george1421 said in New to Fog + Tough scenario :

@thiagotw Well the post I provided with the ltsp.conf file explains how to build the file from the source image. You can do it that way (and was required before the linux distributions supported 2.76 and newer). But its better off to use your distributions dnsmasq package if its new enough. I don’t run ubuntu (rhel guy myself) so I’m a bit conflicted with what you have installed vs what your software catalog shows.

And I am not a Linux guy at all the closest thing i use in my day is pure Pfsense haha!

I can download the 17.04 Ubuntu real kick and reinstall it, since it is a fresh install anyway. At least i can cover future incompatibility problems i guess.

[george1421]

@thiagotw I provided some additional guidance via FOG DM (look at the talk bubble in the fog tool tray)

[george1421]

@george1421 I had a lengthy chat session with the OP. I also remoted in with teamviewer to look at his install. His install of Ubuntu was a bit confused and Ubuntu’s desire to have NetworkManager take over the management of dnsmasq added a bit of complexity to getting this up and running. Per our discussion I was going to look to see if linux mint was a better choice than ubuntu 16.04. In a way it is and in a way its the same.

I was able to install FOG on linux mint 18.2 without any issues. I was able to unhook dnsmasq from NetworkManager without breaking dnsmasq. So I have a process on how to upgrade the native dnsmasq 2.75 to 2.77 that will work reliably.

In the end the OP’s goal is to make a mobile deployment server he can take to remote sites, plugin and image computers. He won’t have access to the remote site’s dhcp server so he does need dnsmasq to overrride any settings that the remote site has for pxe booting. There is still a chance it won’t work in all situations, but I feel confident that it should work in most.

So the recommendation I have for the OP is that you can install Ubuntu 16.04 or 17.04, or Linux Mint 18.2 and we can make it work. We will also need Wayne’s mobile fog script from here: https://github.com/FOGProject/fog-community-scripts to complete the mobile FOG setup.

[thiagotw]

@george1421 It Worked !! Hail George, savior of the nine realms.

Trough TeamViewer, George did a “bit” (alot) of work on dnsmasq, and we see the requests, act, through Wireshark I think he will make a new topic with all process to help others, also for my future replications

[george1421]

@thiagotw Hey I’m glad we were able to get it worked out. And I have to say, your graphic is way cooler than my avatar!! Maybe someday I will get that good with graphics to update my avatar.