Hi Kristian,
You can write and use a custom hook to personalize options for each
client (mac-address). Probably, there another way too.
Juan
El 23/1/19 a las 11:26, Kristian Pedersen escribió:
Hi KEA list,
I'm attempting to mirror this ISC DHCP construct, where the
bootfile-name is set based on the DHCP client mac-address:
subnet x.y.z.0 netmask 255.255.255.0 {
..
pool {
..
option bootfile-name = concat(
suffix (concat ("0", binary-to-ascii (16, 8, "",
substring(hardware, 1, 1))),2),
suffix (concat ("0", binary-to-ascii (16, 8, "",
substring(hardware, 2, 1))),2),
suffix (concat ("0", binary-to-ascii (16, 8, "",
substring(hardware, 3, 1))),2),
suffix (concat ("0", binary-to-ascii (16, 8, "",
substring(hardware, 4, 1))),2),
suffix (concat ("0", binary-to-ascii (16, 8, "",
substring(hardware, 5, 1))),2),
suffix (concat ("0", binary-to-ascii (16, 8, "",
substring(hardware, 6, 1))),2)
);
}
}
How can I achieve something similar using KEA? We use this for per
modem/cpe configuration-files for docsis and other types of devices.
Defining a host entry for every modem/cpe is not really feasible.
I tried a construct similar to this, but could not get it working:
"subnet4": [
..
"option-data": [ {
"name": "boot-file-name",
"data": concat('foo', 'bar')
} ]
]
Kind regards,
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
