On 27/11/2019 10:09, [email protected] wrote:
That's it; I need to give this to DHCP clients as a simple ascii text
string but I can't find a piece of documentation which tells me how to
do this. My attempts at configuring it always end up with an error.
What kind of error - does KEA itself report an error? If so, what does
the error message actually say?
Or does KEA accept it, but your client device doesn't receive the
attribute, or not in the format it expects? In that case, what does
tcpdump show?
This is what I currently have:
"subnet4": [
{
"subnet": "192.168.2.0/24",
"option-data": [
{
"name": "AP-option",
"code": 191,
"data": "pool1=192.168.2.249;level=1"
}
],...
}
https://kea.readthedocs.io/en/v1_6_0/arm/dhcp4-srv.html#custom-dhcpv4-options
Try:
"Dhcp4": {
"option-def": [
{
"name": "AP-option",
"code": 191,
"type": "string",
"array": false,
"space": "dhcp4",
}, ...
Then under the subnet:
"option-data": [
{
"name": "AP-option",
"code": 191,
"space": "dhcp4",
"data": "pool1=192.168.2.249;level=1"
}, ...
(Aside: I don't know why the code and space are duplicated in
option-data, even though they've already been defined in option-def, but
that's what the examples show)
HTH,
Brian.
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
