I'm taking another stab at evaluating Kea (1.3.0) and am seeing an issue that I
saw earlier with respect to Vendor Encapsulated Options (option 43).
With the old ISC DHCP, I can define something like this:
option MitelVendorOptions code 43 = string;
option MitelVendorOptions
"id:ipphone.mitel.com;sw_tftp=10.150.5.32;call_srv=10.150.5.32,10.150.95.34";
The packets to the phone with then have the form 0x2b (43) <some_length> <the
string>
With Kea, I have yet to find a way to replicate this sicne I HAVE to specify a
code. The option then becomes:
0x2b (43) <some_length> <option code I must specify> <another length> <the
string>
This extra is causing some phone models to behave incorrectly.
Q: How can I achieve this?
Here's a snippet of my configuration:
"option-def": [
{
"name": "mitel-options",
"space": "vendor-encapsulated-options-space",
"code": 1,
"type": "string",
"space": "mitel"
}
...
"option-data": [
{
"name": "mitel-options",
"space": "mitel",
"data":
"id:ipphone.mitel.com;sw_tftp=10.151.75.34;call_srv=10.151.75.32"
},
{
"name": "vendor-encapsulated-options"
}
]
Thanks,
Rob
Rob Sutherland
Senior Software Developer - Silhouette R&D | Windstream
[email protected]<mailto:[email protected]> |
broadviewnet.com
o: 973.848.8811
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
