pfSense

I was able to replicate this from a stock config with just three changes:

• Network booting checked
• HTTPBoot URL defined
• One static mapping entry on the interface

Without a static mapping, there was no error.

It appears to be trying to reuse the global numbered options for the static mapping but forming the name incorrectly or failing to re-define it. Not exactly clear yet.

Here is the entire generated configuration:

option domain-name "home.arpa";
option ldap-server code 95 = text;
option domain-search-list code 119 = text;
option arch code 93 = unsigned integer 16; # RFC4578
option custom-lan-0 code 60 = text;

default-lease-time 7200;
max-lease-time 86400;
log-facility local7;
one-lease-per-client true;
deny duplicates;
update-conflict-detection false;
authoritative;
class "s_lan" {
    match pick-first-value (option dhcp-client-identifier, hardware);
}
subnet 192.168.1.0 netmask 255.255.255.0 {
    pool {

        range 192.168.1.100 192.168.1.199;
    }

    option routers 192.168.1.1;
    option domain-name-servers 192.168.1.1;
    ping-check true;

    option custom-lan-0 "HTTPClient";
    if substring (option vendor-class-identifier, 0, 10) = "HTTPClient" {
        filename "http://10.34.0.55:1234/tftp/ipxe.efi";
    }

}
host s_lan_0 {
    hardware ethernet 90:ec:77:47:5e:58;
    fixed-address 192.168.1.9;
    option host-name "blah";

    option custom-s_lan_0-0 "HTTPClient";
}
subclass "s_lan" 1:90:ec:77:47:5e:58;

Note that in the definition at the top and on the interface it's custom-lan-0 but in the static mapping the name is option custom-s_lan_0-0.

Looking at the code it appears to be using the wrong variables for that section, it's checking the pool config when it should be checking the static mapping config.

So not only was this breaking HTTPBoot in general with static mappings, but it also was preventing that option from being used on a per-mapping basis. Fix coming momentarily that addresses both.

Applied in changeset e5e1e8f9c498e1e5094394a049bb62d09ec8e034.