So, Ubuntu 16’s default repository is now 1 point away from dnsmasq version 2.76.
As soon as all of the major distributions are including 2.76 in their default update repositories, then compiling your own will mostly be un-needed, and this will also greatly simplify the process of adding UEFI support to the MakeFogMobile project which utilizes dnsmasq.
Dnsmasq version 2.75 Copyright (c) 2000-2015 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.
So if you look at the above, it collects a username and password on the login screen.
Then, it chains to boot.php and passes the parameters. The web server validates the credentials and if they are good, it provides the full menu via the chaining.
@george1421 I often see it when installing fog inside a vm. I install fog a lot so that makes sense. I think whatever it is isn’t with fog or fos, but with the latest Linux kernel, there’s something up with its display stuff when under load.
@george1421 nice write-up - think this needs updating to be inline with hostinfo.php variables?
Thank you for your kind words.
Yes, looking over the code its a bit dated. There are a few things that while they work, could use a fixup because I don’t think they work as well as it should.
Possibly include setting the host name with this snippet. So they host name can be anything and sed will just swap it out. In the one I wrote for my business it is setup for global deployments. It will identify the local subnet where its being installed and update the timezone, system mui language and keyboard settings for the local region. But the point is they all use a variant of the sed script below.
sed -i -e "s#<ComputerName>\([^<][^<]*\)</ComputerName>#<ComputerName>$hostname</ComputerName>#gi" $unatendfile
In this section we will create a template host where we will hang all of our configuration on. The template host in this context is just a manually registered host with a unique (impossible) mac address. This host will never be used directly for pxe booting or configuring a target host so we will pick a mac address that is unique to your install.
From the perspective of configuring the host template system we will treat it like any other host. We can connect snapins, assign AD parameters, customize fog modules. Everything you can define for a regular host you can do to this host template (except boot it).
To create the host template (hint: its the same process as manually registering a host)
Go to Host Management -> Create New Host
Host Name: TemplHost01 (this name can be anything as long as its locally unique)
Primary MAC: 00:00:00:00:00:01 (The host record MUST contain a mac address, we’ll just set it to a locally unique value.
Fill out the remainder of TemplHost01 as you see fit for your site.
When the settings are correct for your site press the ADD button
After the TemplHost01 has been registered you may now continue configuring this host by adding printers, snapins, and service settings.
This concludes setting up the host template.
The FOG Service on the host PC would pull from the information/data we have on the FOG server for printers, snap-ins, etc. correct?
Right. You have to install this on your reference machine prior to image capture of course, and ensure it’s working before capturing by looking at the log file, typically located at C:\fog.log. The FOG Client is what enables lifetime management of hosts registered with the FOG Server.
This basically makes FOG 1.3.0 completely mobile, it allows the FOG server to receive a DHCP address, and then scripts automatically update FOG’s files, database, and automatically re-configure dnsmasq to work with the new IP.
@george1421 I’d like to work with you to get this side project to work with UEFI too, only problem is if we do that, maybe we need to include an actual dnsmasq binary for x86_64, and after the project installer installs dnsmasq, it just swaps out the binary file all sneaky like lol. At least until the current latest dnsmasq version is mainstream.
@marcolefo The sleep 5 you’ve added will only happen if the $imgpart is not found. This seems rather pointless if you ask me. (Again following along @Sebastian-Roth I’m not intending to offend, but why does having sleep 5 in a spot where no code is run to begin with “help” a user with multi partition imaging via multicast?