<div dir="ltr">Hi Rob,<div><br></div><div>Thank you for the info. I think this would work although our customer we are integrating a solution for claims that his requires option 125 specifically. I'm not sure that is necessarily true but that is what he is claiming based on his previous server setup. If I can't figure out how to get the vendor identifying options working I will get them to test out option 43 as you configure it above.</div><div><br></div><div>I'm curious if there is a way to get option 125 working to encapsulate the right vendor ID with the options included. From the docs I believe Kea allows it and I think I have it configured correctly above but it's only sending out an empty option.</div><div><br></div><div>Thanks again,</div><div><br></div><div>Evan</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Nov 7, 2019 at 10:23 AM Sutherland, Rob <<a href="mailto:Robert.B.Sutherland@windstream.com">Robert.B.Sutherland@windstream.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_6867817071788775865WordSection1">
<p class="MsoNormal">Here’s what worked for my Mitel phones (note that I used option 43):<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"> "client-classes": [<u></u><u></u></p>
<p class="MsoNormal"> {<u></u><u></u></p>
<p class="MsoNormal"> "name": "mitel",<u></u><u></u></p>
<p class="MsoNormal"> "test": "substring(option[60].hex,0,17) == '<a href="http://ipphone.mitel.com" target="_blank">ipphone.mitel.com</a>'",<u></u><u></u></p>
<p class="MsoNormal"> "option-def": [<u></u><u></u></p>
<p class="MsoNormal"> {<u></u><u></u></p>
<p class="MsoNormal"> "name": "vendor-encapsulated-options",<u></u><u></u></p>
<p class="MsoNormal"> "code": 43,<u></u><u></u></p>
<p class="MsoNormal"> "type": "string"<u></u><u></u></p>
<p class="MsoNormal"> }<u></u><u></u></p>
<p class="MsoNormal"> ],<u></u><u></u></p>
<p class="MsoNormal"> "option-data": [<u></u><u></u></p>
<p class="MsoNormal"> {<u></u><u></u></p>
<p class="MsoNormal"> "name": "vendor-encapsulated-options",<u></u><u></u></p>
<p class="MsoNormal"> "data": "id:<a href="http://ipphone.mitel.com" target="_blank">ipphone.mitel.com</a>;sw_tftp=10.151.75.34;call_srv=10.151.75.32"<u></u><u></u></p>
<p class="MsoNormal"> }<u></u><u></u></p>
<p class="MsoNormal"> ]<u></u><u></u></p>
<p class="MsoNormal"> },<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b>From:</b> Kea-users <<a href="mailto:kea-users-bounces@lists.isc.org" target="_blank">kea-users-bounces@lists.isc.org</a>> <b>
On Behalf Of </b>Evan Carson<br>
<b>Sent:</b> Wednesday, November 6, 2019 4:00 PM<br>
<b>To:</b> <a href="mailto:kea-users@lists.isc.org" target="_blank">kea-users@lists.isc.org</a><br>
<b>Subject:</b> [Kea-users] Vendor-Identifying option 125 vivso-suboptions<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">Hello,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We are running Kea 1.4.0 and are having trouble getting the server to hand out option 125 to a Mitel phone. The Kea server is replying to the client with this data in the DHCP offer with an empty option 125 containing only the Mitel enterprise
option but no data.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We have this option definition specified in the Dhcp4 config:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> "option-def": [<br>
{<br>
"array": false,<br>
"code": 130,<br>
"encapsulate": "",<br>
"name": "mitel-option",<br>
"record-types": "",<br>
"space": "vendor-1027",<br>
"type": "string"<br>
}<br>
],<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We then placed this option in the subnet["pools"]["option-data"] for our phone subnet<u></u><u></u></p>
</div>
<p class="MsoNormal"> {<br>
"name": "vivso-suboptions",<br>
"data": "1027"<br>
},<br>
{<br>
"name": "mitel-option",<br>
"space": "vendor-1027",<br>
"data": "id:<a href="https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fipphone.mitel.com&data=02%7C01%7CRobert.B.Sutherland%40windstream.com%7Cfe63ef71459047eeb95b08d762fc465b%7C2567b4c1b0ed40f5aee358d7c5f3e2b2%7C1%7C1%7C637086707970887653&sdata=ybRRfpPu13cnOyzXLUV2ojFqrTIFjusuUu%2BijhCjs1s%3D&reserved=0" target="_blank">ipphone.mitel.com</a>;sw_tftp=10.78.182.2;call_srv=10.78.182.2;vlan=71;l2p=6;dscp=46;"<br>
}<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Here is the DHCP Offer pcap coming back from server:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt">Frame 15952: 332 bytes on wire (2656 bits), 332 bytes captured (2656 bits)<br>
Ethernet II, Src: RealtekU_e9:ea:63 (52:54:00:e9:ea:63), Dst: SmcStand_9c:c6:36 (08:00:0f:9c:c6:36)<br>
Internet Protocol Version 4, Src: 192.168.1.1, Dst: 255.255.255.255<br>
User Datagram Protocol, Src Port: 67, Dst Port: 68<br>
Bootstrap Protocol (Offer)<br>
Message type: Boot Reply (2)<br>
Hardware type: Ethernet (0x01)<br>
Hardware address length: 6<br>
Hops: 0<br>
Transaction ID: 0x99cc086f<br>
Seconds elapsed: 0<br>
Bootp flags: 0x8000, Broadcast flag (Broadcast)<br>
Client IP address: 0.0.0.0<br>
Your (client) IP address: 192.168.1.102<br>
Next server IP address: 0.0.0.0<br>
Relay agent IP address: 0.0.0.0<br>
Client MAC address: SmcStand_9c:c6:36 (08:00:0f:9c:c6:36)<br>
Client hardware address padding: 00000000000000000000<br>
Server host name: KVM_128T_Remote<br>
Boot file name not given<br>
Magic cookie: DHCP<br>
Option: (1) Subnet Mask<br>
Option: (3) Router<br>
Option: (6) Domain Name Server<br>
Option: (51) IP Address Lease Time<br>
Option: (53) DHCP Message Type (Offer)<br>
Option: (54) DHCP Server Identifier<br>
Option: (61) Client identifier<br>
Option: (125) V-I Vendor-specific Information<br>
Length: 5<br>
Enterprise: Mitel, Corp. (1027)<br>
Length: 0<br>
Option: (255) End<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">It looks like the configuration for the enterprise ID is working correctly however the custom "mitel-option" string doesn't seem to be contributing. Is there anything wrong with the way we have this configured?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We aren't using any client-class configuration to restrict this option to only the clients requesting a given Vendor-Identifying Vendor Class option. Is it a requirement that the client-classification be used to specify the vendor class
option?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thank you for your help,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Evan Carson<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="gmail-m_6867817071788775865msipfooter10100105" style="margin:0in 0in 0.0001pt"><span style="font-size:8pt;color:black">Sensitivity: Internal</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote></div>