@rlair23 I’ll raise your tutorial with one of my own: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

The next step is indeed to get a pcap of the pxe booting process. You can either use wireshark on a witness computer or for a bit more information since the pxe booting computer and fog server is on the same subnet use tcpdump on the fog server. This will collect both the broadcast and unicast messages between the fog server and target computer.

You can either look at the pcap or post it to a file share site and DM me the link in the fog project chat. If you want to look at it I can give you where to look, though it would be quicker if I looked at it because there are a few exceptions.

@rlair23 said in PXE-E99: Unexpected Network Error:

the pxe rep

Not sure I understand “rep”.

Secure boot is a setting on the pxe booting computer in the firmware settings.

The unexpected network error bugs me. But first lets check the basics since this is a new install.

@rlair23 dhcp options 66 and 67 need to be set for basic pxe booting. The issue with dhcp option 67 is that if you need to boot uefi you need to enter ipxe.efi. If you want to pxe boot a bios client you need to change the value to undionly.kpxe. That is the static way of doing it.

The bios uefi coexistence wiki tells you how to setup profiles to give you a dynamic pxe booting. Does it need it, no. Does it make your life easier if you have a mixed environment, yes.

Since this is a new install.

1. Make sure the unbuntu firewall is disabled.
2. On the client computer make sure secure boot is disabled.

We may need to get a packet capture of the pxe boot process to understand what is going sideways.

If you have more than one dhcp server (such as a fail over dhcp server), make sure you set the options in both servers

@rogalskij FOG uses the distribution’s tftp server. This is to ensure the services used by FOG is supported by your linux distribution vendor.

@rogalskij Using a windows computer, install the tftp client feature. Turn off the windows firewall then open a command window to see if you can tftp get the file ipxe.efi. I’m only interested if it downloads the file or not.

@rlair23 Is this a new FOG install or it has always worked but now it doesn’t. I’m trying to understand did it ever work?

@rlair23 Did you turn on https on the fog server for some reason?

Is 10.10.11.33 indeed your fog server’s IP address?

@jj-fullmer So how would you propose to tweak this code:

#!/bin/bash
ceol=`tput el`;
manu=`dmidecode -s system-manufacturer`;
dots "Identifying hardware"
case $manu in
    [Ll][Ee][Nn][Oo][Vv][Oo])
        machine=$(dmidecode -s system-version)
        ;;
    *[Dd][Ee][Ll][Ll]*)
        machine=$(dmidecode -s system-product-name)
        ;;
    *I[Nn][Tt][Ee][Ll]*)
        # For the Intel NUC and intel mobo pick up the system type from the
        # baseboard product name
        machine=$(dmidecode -s baseboard-product-name)
        ;;
    *)

ref: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

I need to look because someone else just recently found a bug in this section of code too. Maybe I need to update/create a 2022 version of this post. The 2017 version is still accurate even in 2022 (maybe)

@jape Do you have control of your subnet router? If yes can you add a dhcp server (fog server’s IP address) to the dhcp-helper/relay service in the router?

The thought is to provide just pxe boot info we will use dnsmasq. The only thing is if you have multiple ip subnets, the dnsmasq service needs to hear the pxe boot request. It will only provide pxe boot info everything else comes from your main dhcp server. We use this method when the dhcp server can’t be modified or is broken and can’t provide the proper pxe boot info.

@geekyjm

ref: https://forums.fogproject.org/post/120405

@jape said in FOG unable to PXE boot beyond the VLAN/subnet that the server is on:

So perhaps that will complicate things

Yes it will. dhcp works off from broadcast messages, so it communicates by sending out broadcast messages on the same vlan/network. Having 2 dhcp servers on the same network segment will cause you grief.

Fog can integrate into an environment where there is an existing dhcp server no problem. FOG’s internal dhcp server would be typically used if you were to setup an isolated imaging network where there was no device except the pxe booting computer and the fog server.

So lets start out with this, what device is your preexisting dhcp server?

@jape Just to be clear you did not have a preexisting dhcp server on your site until fog was installed? Not even a router or other device that acted in place of a traditional dhcp server? its a bit strange (I feel) that you would have vlans/subnets without an existing dhcp server.

If this is true, no worries its pretty simple to get the remote subnets to work.

@geekyjm If I remember correctly the certificate is in /opt/fog/ssl ( I think ) but it is in /opt/fog directory or below. be sure to rename the original certificate on the new fog server before you copy over the old certificate. Once copied over reboot the fog server computer.

@geekyjm said in postdownload script:

Is there a new postdownload script I could download and try?

First let me say that post download scripts have nothing to do with Windows or connecting to AD. Your issues are probably not the root cause.

Lets assume you have the FOG client connect the target computer to AD (there are other ways to got about it, but most use the fog client) and you have just changed fog servers.

My bet is that the fog client can no longer talk to the new FOG server, and hence not get the instructions to connect to AD.

When the fog client is installed (like on the precaptured golden image), it tattoos itself to the fog server’s certificate. That certificate is unique to each install of FOG. My bet is that you didn’t copy over the certificate from the old fog server to the new fog server. So the clients are rejecting the new FOG server because the certificates don’t match.

@danibashkov Try single disk non-resizable. Lets see if you can get it past that error. I did find a reference from 2016 on the forum with the same error.

ref: https://forums.fogproject.org/topic/8602/cannot-upload-neverware-cloudready-chromeos-to-fog-e2fsck-failed-to-check-dev-sda20-shrinkpartition

@lacugo If you switch over to the FOG 1.5.9 dev branch (a.k.a FOG 1.5.9.115) it will install cleanly on Debian 11. But sadly not ubuntu 22.04 or centos 8 where php8 is the default install. AS of now FOG only supports PHP7.x until some code refactoring is done.

@rav ok here is the updated file: https://drive.google.com/file/d/1_pJWzun8R5v-PdMWk0j_l1dt8qEZzpjC/view?usp=sharing

What I did here is I see your fog server is at 192.168.5.234. In the config file I set the next server value to 192.168.5.234 The boot file is set dynamically by the config file. The dhcp range (what the isc dhcp server will hand out) is 192.168.5.10 to 192.168.5.200.

replace the existing config file with this one.

At the fog server’s command prompt (su to root to do this).

Issue these commands.
First to stop and then restart the isc-dhcp server (this will load in the new config file)
systemctl restart isc-dhcp-server

wait about 10 seconds

Now lets get the status of the dhcp server.
systemctl status isc-dhcp-server

Hopefully somewhere in the wall of text it will say running.

Now lets ensure that the dhcp server will startup at boot time.
systemctl enable isc-dhcp-server

@rav OK let me work on the file and get it back to you. The short answer is the network defined in the dhcp server is not the same as your fog server network interface.

@rav The config file you provided is for the dhcp client (app that runs on your computer that contacts the dhcp server). the file we are looking for is this: /etc/dhcp/dhcpd.conf

@rav said in Cannot get iPXE to connect to FOG Server:

Do I put “ip a s” at the end of the code?

Sorry I should have been more clear. On the fog server linux console run that command. It will list out the network adapters configured in your computer.