Posts made by george1421

@eazis Ok, when you use industry specific key words like ‘quarantine’, I wanted to make sure there wasn’t something more going on here than expected.

So for your business network, you want to do point to point (unicast) imaging only? If you want to do multicast imaging your router between the two subnets must support multicast routing.

OK to your initial question. The issue you have is your dhcp server on your business network doesn’t support dynamic boot files. If you want to pxe boot both uefi and bios (legacy mode) computers, your dhcp server needs to be smart enough to send the appropriate boot file based on the pxe booting client computer. In the case of the fog server, it uses isc-dhcp server which has a specific configuration to dynamically switch between the two boot files.

So if your dhcp server doesn’t support this you can use a ProxyDhcp server (like dnsmasq) to only supply the pxe booting information. This is not a dhcp server replacement (it can be, but not in this instance), but a dhcp add on function called ProxyDHCP. Where the dnsmasq server listens for a discover request from a pxe booting client and sends out a ProxyDHCP offer in addition to your primary dhcp server sending out a dhcp offer.

Dnsmasq (or any other ProxyDHCP service) can run on the fog server, or on a windows or linux box on your business network.

Before I can give you a clear answer, can you tell me why the FOG server is on the quarantine network? What problem are you trying to solve here?

Is there any type of network IP routing between the two networks?

You may want to look into (not ranked in any order) GLPI, Spiceworks Inventory, or even PDQ Inventory. With the FOG 1.x release CMDB is not a feature.

@steuve68 One other test you should check, is if the FOG Admin changes his/her password. Is that password change seen immediatly by the fog server? I’m only suggesting this based on your #2 point of the one shot after the admin has been removed.

You have 2 issues here.

1. Multicast: If you have a fog server on one vlan and your target computers on a different vlan you must make changes to your vlan router to support multicast routing or you need to install a multicast router (mrouter). Multicasts are not typically forwarded by default on many vlan routers. I would focus on your vlan router to understand why its not forwarding multicast packets.

2. “downloaded WDSNBP…” Windows deployment services: You have a WDS server configured on this vlan. The WDS server is overriding your pxe boot information on this vlan. Turn off the wds server and your network booting via FOG will work better.

Two things come to mind.

1. Does ipxe display the mac address of the wireless nic? If it does then move on to #2
2. Check to see if spanning tree is enabled on that network switch port. If it is either enable one of the fast STP protocols or place a unmanaged (dumb) switch between your building switch and the target computer as a test. If it boots into FOS then you do have a spanning tree (network) issue.

@rj7658 Another solution (which we used before fog supported resizable disks) where to create the reference image in a VM with the disk smaller than the smallest size we had in our environment. So at the time we created our reference image on a 40GB virtual disk. Captured and deployed with FOG, then in the setupcomplete.cmd piped some commands into diskpart to expand the disk to the size of the target hard drive.

You could use a similar concept by creating your reference image on an artificially small hard drive, capture with FOG single disk resizable, then when FOG deploys to a target system it will expand to the size of the target hard drive.

@lof The best solution (IMO) for a mobile deployment server is to run dnsmasq on your fog server. That way regardless of the target environment, as long as your fog server is connected IT will be the pxe boot server. As soon as you unplug your mobile deployment server the target network will go back to what ever is currently configured in dhcp options 66 and 67. The only risk to the target environment is if they have voip phones that need to be provisioned via a pxe boot PBX AND they happen to reboot when your fog server is installed. They might not get their config file from the pbx. Its kind of a small risk, but still a risk.

@lof you will probably want to install dnsmasq on your fog server and have the make fog mobile script manage that too. That way you can supply pxe boot information to your client network and still have a VMware that is assigned by dhcp address.

@dpotesta50 said in Fresh Install of Fog - Setup PXE Boot:

192.168.100.100/fog/management

This will only work if you are on the imaging network, to access the managment interface from the business side you will need to find the IP address of the wifi adapter.

@dpotesta50 Did you remember to disable the ubuntu firewall and set the selinux permissions to permissive as recommended in the prerequisites?

@dpotesta50 OK so why can’t you connect to both wifi and ethernet? Is this a laptop where you have the bios (firmware) setup to disconnect wifi if the ethernet cable is connected?

@dpotesta50 No since you have an isolated network

@dpotesta50 OK once your wired ethernet has a real IP address AND you have access to the internet using the wireless interface you can go ahead and install FOG. Just be sure to select your wired connection during setup and you should be good to go.

@dpotesta50 Then ip addr show now shows the proper IP address for interface enp2s0 ?? I don’t need to see it, just want to confirm that you see it.

@dpotesta50 enp2s0 is your wired ethernet adapter and should be your FOG default adapter. But your don’t have an IP address range assigned just yet. Don’t install FOG.

It looks like your wireless interface is connected to 192.168.50.x network. Is that right?

@dpotesta50 said in Fresh Install of Fog - Setup PXE Boot:

on the part of the installation that asks if I want to change the default network interface. How do I know which it’s default to?

OK then back to where you were.

The default network adapter will be your imaging network adapter. You can view this by the following command on the fog server linux command prompt
ip addr show That will show you all network interfaces. The one with teh IP address that matches your imaging network is the one you want to set as your default. It may be named eth0 or something else based on your linux distro.

@dpotesta50 So if your clients use MS dhcp server then there is no reason to have a dedicated imaging network (understand there ARE reasons to have a dedicated imaging network, I just want to see if your use case fits).

You do not need to use fog dhcp server at all. It is provided when your needs are specific. As long as you can configure dhcp options 66 and 67 in your MS dhcp server then you are good to go. If you have a mix of uefi and bios (legacy mode) computers you will need a windows 2012 or newer dhcp server to create the filters to dynamically switch between the boot files. This isn’t a requirement, but it makes life easier for you.

@dpotesta50 There is no real simple. For the clients to get their dhcp addresses from your business network you will need to have a router setup to pass the dhcp requests to your dhcp server.

Lets take a step back, why do you feel you need a dedicated imaging network?

@dpotesta50 OK once you get unbuntu reinstalled. Setup eth0 (or what ever your ethernet adapter is) on your imaging network. Do not give it a gateway address since its on an isolated network. Give it an IP address unique to your imaging network.

Then connect your second network adapter (wifi in this case) to your business network and give it a default gateway so the fog installer has internet access. Its only needed during installation to download the latest kernels. Post install you will use it for FOG administration if needed.

Now when you install FOG only bind it to your ethernet interface on your dedicated imaging network. FOG will not connect to wifi unless you tell it. Once FOG is installed if you want to double check to make sure it didn’t bind to the wireless interface we can look at the isc-dhcp config file.

But in general, if you don’t tell fog about your wifi interface it will not use it.

FWIW, FOG works perfectly well using a ms windows dhcp server too.