Trouble importing DHCP Mappings from 2.6 to 2.7.2

Seeking Sense

ORIGIANAL POST

Is it possible to import DHCP Mapping from 2.6 to 2.7.2?

Attempted using the GUI but with no success.

Second approach was to manually edit the config.xml but that was also unsuccessful.

UPDATE

There were two issues.

There was some extraneous data in the XML file.
It appears that VLANS / interfaces need to be up for the ability to import associated IP mappings. They are not up the import fail and the config file reverts to the last working config.

Gertjan

@Seeking-Sense said in Trouble importing DHCP Mappings from 2.6 to 2.7.2:

It appears that VLANS / interfaces need to be up for the ability to ....

The DHCP server config files only get created, and the server started if the interface on which is should be listening, exists and is active.
No need to run a server on an interface that doesn't exist ^^

What is the use of having DHCP MAC Leases on an interface that doesn't exist ?

Seeking Sense

@Gertjan said in Trouble importing DHCP Mappings from 2.6 to 2.7.2:

What is the use of having DHCP MAC Leases on an interface that doesn't exist ?

Touché.

But existing and enabled are or should be two different things.

I have them created but not enabled.

I am in the process of migrating to new hardware which is plugged into the same network as the active router running 2.6 and just working my way through configuring the new hardware running 2.7.2.

Once complete I will transition the WAN and go live with the new hardware.

One other issues I have come across is that KEA DHCP causes issues throwing PHP errors / crash reports in conjunction with pfblockerng dev.

Gertjan

@Seeking-Sense said in Trouble importing DHCP Mappings from 2.6 to 2.7.2:

But existing and enabled are or should be two different things.

When an interface is not connected (you ripped out the network, or powered down the device or switch on the other side), the DHCP server serving that interface will detect the "DOWN" system / hardware event, and shut down.
pfSense won't even show you your DHCP server instance anymore.
But, no panic, the settings will still be there. And when you connect (power up) the connection, it will auto-start, with the previously known settings.

@Seeking-Sense said in Trouble importing DHCP Mappings from 2.6 to 2.7.2:

One other issues I have come across is that KEA DHCP causes issues throwing PHP errors / crash reports in conjunction with pfblockerng dev.

kea initially, when using 23.09 ? I can't recall, work fine but the implemention'27.2' (and 23.09, 24.03, before 24.11 came out) was, for my needs, to minimalist.
You can use Kea, if you validated your requirement first.

Here they are : Netgate Adds Kea DHCP to pfSense Plus Software Version 23.09

As you can see, the details are here - published November 2023 :

So, you need "static MAC DHCP leases" ?
Ok, fine. Stick with ISC for the moment.

Right now, 24.11 adds static DHCP leases, DNS registration, but is still limited about adding your own DHCP options.
The upcoming 2.8.0 will have the same Kea support.

Btw : kea by itself was and is rock solid for me. It had to stick with ISC because I wanted to keep my DHCP mac leases, my DHCP special options etc, but since 24.11 became available, I switched to kea. Options were still missing but with some copy and paste instructions from the source' (redmine) I could add what I needed.

Btw : kea has no relations with pfBlockerng.