Hi, thank you for taking the time to read this.

We have FOG on subnet 192.168.3.0/24, and we use it for imaging laptops that go for sale. On the subnet 192.168.2.0/24, we have AikenWorkbench that we use to test those laptops before imaging. Aiken has its own DHCP server and uses pxelinux.0 and grub if I understand correctly.

We would love to have both servers on a single subnet. So we won’t need to double the ethernet cables and unplug them every time a task is done.

What would be the approach to achieve that?

1. Having them both running on Type 1 Hypevisor or Containers? If this is even possible.
2. Having two servers on the same subnet pointing to each other?
3. Having them on separate subnets pointing to each other?

AikenWorkbench has a lot of proprietary code they don’t share, and their customer support says this is not possible to have another PXE server working along with theirs.
I was trying to install FOG along with Aiken, but I ran into some problems with SQL and FOG installation failed. Aiken uses SQL, and I don’t have the password for it. Also, we have only one licence, so no staging is possible.

I have also tried Aiken grub.cfg to point to FOG, which failed. Then I tried Chainloading PXE to iPXE using pxelinux.0 and that completely broke Aiken. Had to restore from backup (which is in Acronis, not FOG, as they conflict)

I know nothing about PXE, iPXE and pxelinux.0. I know very little about DHCP and more about grub. I’m willing to learn, though. So if you could point me in the right direction and docs, I would really appreciate that.

Here is a part of the dhcpd.conf:

class "pxeclients" {
     match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
     next-server 192.168.2.1;
     if (option arch = 00:00) {
         filename "bios/pxelinux.0";
     }elsif (option arch = 00:06) {
         filename "grub/bootx32.efi";
     }elsif (option arch = 00:07) {
         filename "grub/bootx64.efi";
     }

Regards
Damian