Inquiry Regarding Integration of Kea DHCP with DOCSIS Cable Modem DHCP Requests

"Fernando R. Soto" <[email protected]> Wed, 29 Nov 2023 16:23:45 -0300
Newsgroups gmane.network.dhcp.isc.dhcp-client
Message-ID <[email protected]>
This is a multipart message in MIME format.

--===============2472838756674803850==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_04DF_01DA22E0.6DDED630"
Content-Language: es

This is a multipart message in MIME format.

------=_NextPart_000_04DF_01DA22E0.6DDED630
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear ISC Support Team,

 

I hope this email finds you well. I am reaching out to seek guidance on
integrating Kea DHCP with DHCP requests originating from DOCSIS cable
modems.

 

My inquiry revolves around configuring the DHCP Server to, upon receiving a
DHCP Discover and detecting that it originates from a cable modem, utilize
the client-class option as follows:

"client-classes": [

    {

        "name": "Cablemodem",

        "test": "substring(option[60].hex, 0, 6) == 'docsis'",

        "next-server": "192.168.10.43",

        "boot-file-name": "default.bin"

    }

],

 

The goal is for Kea DHCP, in responding to the boot-file-name, to execute a
query against an SQL table. This query would seek the MAC address of the
cable modem, present in both the Client MAC address field
("ARRISGro_4c:d4:a2" or "98:6b:3d:4c:d4:a2") and option 82 ("Agent
Information Option"). If the MAC is found in the table, it would fetch the
corresponding value from the boot-file field. If no match is found, the
response would default to "default.bin".

 

I would appreciate any guidance or suggestions you can provide to achieve
this scenario.

 

Thank you in advance for your time and assistance.

 

Best regards,

 

 


------=_NextPart_000_04DF_01DA22E0.6DDED630
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	page-break-after:avoid;
	font-size:14.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	mso-ligatures:none;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES-AR =
link=3D"#0563C1" vlink=3D"#954F72" style=3D'word-wrap:break-word'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'>Dear ISC Support =
Team,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:12.0pt'>I hope =
this email finds you well. I am reaching out to seek guidance on =
integrating Kea DHCP with DHCP requests originating from DOCSIS cable =
modems.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:12.0pt'>My =
inquiry revolves around configuring the DHCP Server to, upon receiving a =
DHCP Discover and detecting that it originates from a cable modem, =
utilize the client-class option as follows:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&quot;client-classes&quot;: =
[<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp; {<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;name&quot;: &quot;Cablemodem&quot;,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;test&quot;: &quot;substring(option[60].hex, 0, 6) =3D=3D =
'docsis'&quot;,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;next-server&quot;: =
&quot;192.168.10.43&quot;,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;boot-file-name&quot;: =
&quot;default.bin&quot;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp; =
}<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'>],<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:12.0pt'>The goal =
is for Kea DHCP, in responding to the boot-file-name, to execute a query =
against an SQL table. This query would seek the MAC address of the cable =
modem, present in both the Client MAC address field =
(&quot;ARRISGro_4c:d4:a2&quot; or &quot;98:6b:3d:4c:d4:a2&quot;) and =
option 82 (&quot;Agent Information Option&quot;). If the MAC is found in =
the table, it would fetch the corresponding value from the boot-file =
field. If no match is found, the response would default to =
&quot;default.bin&quot;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:12.0pt'>I would =
appreciate any guidance or suggestions you can provide to achieve this =
scenario.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:12.0pt'>Thank =
you in advance for your time and assistance.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:12.0pt'>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></p></div></body></htm=
l>
------=_NextPart_000_04DF_01DA22E0.6DDED630--


--===============2472838756674803850==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users

--===============2472838756674803850==--