DHCP-Server is not fog, so how..

[simpsonetti]

Hi, as the subject described it, i have a running dhcp-server with “static” IP, so i got every MAC-address, add them into my dhcp and serve them the same ip. Works fine.
Now i wnat to use fog as imaging solution. I don’t want to use fog as dhcp-server, but how could i change my settings to guide the pxe-menu from my running server, to the fog-pxe-menu to capture my first image and than deploy it?
I will/have to use the fog-pxe.
thanks for some hints.
regards simpsonetti

[Sebastian Roth]

@simpsonetti What kind of DHCP server do you have? Do you have rights to change settings or is the DHCP managed by a different team? In both cases we have a solution for you, just need to known.

[simpsonetti]

@Sebastian-Roth
ISC dhcp and yes, full access to the server.

[Sebastian Roth]

@simpsonetti Check out the wiki article on DHCP configuration including the examples.

Most important part in your case is probably next-server x.x.x.x; and those class "UEFI-32-1" sections with various names.

[simpsonetti]

@Sebastian-Roth
Okay thanks, i will try.
I have here brand new fujitsu d738 with UEFI only. No legacy bios, no CSM. SebureBoot is off.
I hope if my dhcp settings are right, i could capture the image and deploy it…

[simpsonetti]

hm, i add this to my config (i have already a pxe that works with bios and uefi/bios, but not with uefi-only)
The “next-server” should only be in the 172.18 subnet. I think the positino is right, but it didn’t work, the client tries to use the old pxe-server, not fog…
any ideas?

option routers 172.16.0.2;
option ntp-servers 172.16.0.2;
option time-servers 172.16.0.2;
option lpr-servers 172.16.0.4;
option netbios-name-servers 172.16.0.2;
option wpad-curl code 252 = text;
option wpad-curl "http://admin.mydomain.de/proxy.pac";
option arch code 93 = unsigned integer 16;
if option arch = 00:07 {
      filename "efi/grub.efi";
} else {
      filename "pxelinux.0";
}

shared-network "schulnetz" {
        subnet 172.16.0.0 netmask 255.255.0.0 {
                next-server 172.16.0.2;
                pool {
                        range dynamic-bootp 172.16.1.0 172.16.1.25;
                        allow unknown clients;
                        deny  known clients;
                        default-lease-time 300;
                        max-lease-time 600;
                }
        }

        subnet 172.18.0.0 netmask 255.255.0.0 {

                next-server 172.18.2.14;


    class "UEFI-32-1" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
    filename "i386-efi/ipxe.efi";
    }

    class "UEFI-32-2" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
     filename "i386-efi/ipxe.efi";
    }

    class "UEFI-64-1" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
     filename "ipxe.efi";
    }

    class "UEFI-64-2" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
    filename "ipxe.efi";
    }

    class "UEFI-64-3" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
     filename "ipxe.efi";
    }

    class "Legacy" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
    filename "undionly.kkpxe";
    }

[Sebastian Roth]

@simpsonetti Is your DHCP server also a router with different network interfaces for those networks?

[simpsonetti]

yes. there are 2 NICs. one for my educational network, one for our administration. I need this first for our administration

[Sebastian Roth]

@simpsonetti It’s hard to give an answer on why this doesn’t work the way you want it if we don’t know how the full setup looks like. You are using shared-network which I have never used before. I have no idea what consequences this might have. Are those two networks (172.16.0.0/16 and 172.18.0.0/16) on the same physical ethernet? Using VLANs as well? You might want to post the full output of ip a s and your complete dhcpd.conf plus information on VLANs so we get the full picture.

[simpsonetti]

Hi, sorry for the long time without response.
I checked a WDS and this server couldn’t serve too,
Than I put one client in my other dhcp config and tada, it works.
So it’s with the shared-network settings, that at least pxe won’t work. I have this config for now 2 Years an most of the time myself is in “the other net” so i don’t have seen this behavior.

My work around is to put my cloning Pc in the “working” net, image them and than change it to the other net.