In pfSense, just pre-pending

\000

to the string specified in DHCP client configuration ( DHCP Client ID = myhostname as stated in Rob Gormley example )
it works correctly

My test:¶

Settings¶

on pfSense¶

Ver. 2.5.0-RELEASE (amd64)

Services/DHCP Server/LAN/Edit Static Mapping

MAC Address =
Client Identifier = \000test02
IP Address = 192.168.0.218
Hostname =

on raspbian¶

/etc/dhcpcd.conf

clientid test02

clientid "test02" 

Results¶

on pfSense¶

/var/dhcpd/etc/dhcpd.conf

host s_lan_12 {
    option dhcp-client-identifier "\000test02";
    fixed-address 192.168.0.218;

}
subclass "s_lan" "\000test02";

on raspbian¶

I get the correct DHCP values among them IP is 192.168.0.218

Request¶

To me, just prepending \000 to the text content of the GUI field

Services / DHCP Server / LAN / Edit Static Mapping ==> Client Identifier

which should contain the same text as specified in client's DHCP configuration (clientid on debian or MacOs) should solve (or at least work around) the issue and let the feature work flawlessly.

As stated in my previous post, I regularly use it by prepending \000 directly in psSense GUI, and it works fine (in this case the MAC Address filed have to be empty).

In my opinion solving the issue should be now a priority for many sysadmin because of the increasing number of notebooks, or other mobile devices, without a built-in ethernet card, using usb/thundebolt => ethernet adapters that are frequently interchanged between different users on different devices. This way it's not possible to apply specific firewall rules based on the IP Address, that apply to users.

Setting the DHCP clientid parameter on the user's os dhcp configuration it's possible to apply rules precisely to each single user, no matter which network device is used to connect to the network.
This is also the case where users connect either via WiFi or via Ethernet card.

Furthermore, there is the benefit of decreasing the number of IP reservations; 1 IP per client (user Operating Sistem), no more 1 IP per user/network card)

Still present in rel. 2.7.1
The bug have been persisting on all releases in the last 7 years.
While I'm grateful to everyone is working on this project, please, I'd like to know if there is any plan to fix it.

Carlo Tognetti wrote in #note-4:

Still present in rel. 2.7.1
The bug have been persisting on all releases in the last 7 years.
While I'm grateful to everyone is working on this project, please, I'd like to know if there is any plan to fix it.

Hello Carlo,

Have you tested this on 2.7.2 with Kea instead of ISC-DHCP? The formatting for DHCP leases in Kea is completely different and ISC-DHCP is eventually being deprecated.