Topics created by ZrytyADHD

@ZrytyADHD said in Booting accros networks:

You have a number of problems here.

FOG doesn’t like it when you change the fog server’s IP address after FOG is installed. There are several steps that you must do if you decide to change the FOG server IP address after fog is installed.

Why are you mixing WDS and FOG in your booting process? You can do manage it but I would go about it a bit differently.

Your section of the isc dhcp server is just wrong in my opinion.

if exists user-class and option user-class = "iPXE" { filename "http://10.0.0.68/boot.php"; } else { if option arch = 00:00 { filename "undionly-mj2.kpxe"; } else { #UEFI Bootujemy z WDS UEFI next-server 10.249.4.20; filename "boot\\x64\\wdsmgfw.efi" } }

a. I’m not aware of a user class in the dhcp discover packet. There is a vendor class
Vendor class identifier: PXEClient:Arch:00007:UNDI:003016

b. The following line is wrong for several reasons

filename "http://10.0.0.68/boot.php";

b.1 you are telling the PXE rom to load a http protocol. Almost all PXE roms use tftp not http.
b.2 The path to the boot.php is wrong if you are trying to call the boot.php on the fog server the path is <fog_server_ip>/fog/service/ipxe/boot.php

For this I would just use filename "default.ipxe"; but that still will not work because you don’t mention the boot loader (undionly.kpxe or ipxe.efu)

c. You are saying if the option is bios then load undionly-mj2.kpxe (not a fog supplied boot loader) but if everything else call WDS. But only do this if user-class == “iPXE”

d. uefi pxe booting into FOG is not supported

There are ways to fix this, dhcp booting, but please explain why you are mixing FOG and WDS. What is your goal of doing this? Will it be a for ever solution?