DHCPv6 Option 56 configuration

Marek Hajduczenia <[email protected]> Thu, 18 Jan 2024 11:54:55 -0700
Newsgroups gmane.network.dhcp.isc.dhcp-client
Message-ID <CAEoryJcT=3FMk612OD3PeUEiJjKmZzfNGKQvrhe8ir1C7kmgKg@mail.gmail.com>
--===============8148431457597796659==
Content-Type: multipart/alternative; boundary="000000000000699cd4060f3ce8e2"

--000000000000699cd4060f3ce8e2
Content-Type: text/plain; charset="UTF-8"

Dear mailing list users,
I have been trying to define NTPv6 option to use with ISC-DHCPD6 daemon
(4.4.1 running on Ubuntu 22.04 server) as follows

# ntp option 56
option space ntp code width 2 length width 2 hash size 2;
option ntp.address code 1 = array of ip6-address;
option opt56 code 56 = encapsulate ntp;

and then use it in a subnet as follows

shared-network enp7s0 {
    authoritative;
    # deny bootp;
    subnet6 fc00:6ce4:40:146::/64 {
        pool6 {
            # vendor-option-space ntp;
            option ntp.address fc00:6ce4:40:146::1;
            default-lease-time 600;
            min-lease-time 450;
            max-lease-time 900;
            allow all clients;
            range6 fc00:6ce4:40:146::10 fc00:6ce4:40:146::ffff;
        }
    }
}

but no matter what I do, the ISC does not seem to include Option 56 in the
Reply / Advertise messages, even though the client does request Option 56.
I have spent probably 48 hrs in total already, resulting in discovering
that the only thing that seems to be working is a brute force hex encoded
string (example below)

option dhcp6.ntp-servers code 56 = string;
option dhcp6.ntp-servers
00:01:00:10:20:01:0d:b8:0c:a2:00:02:00:00:00:00:00:00:00:01;

Is there any trick to forcing the ISC daemon to include the encapsulation
option?

Thank you in advance

M

--000000000000699cd4060f3ce8e2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear mailing list users, <br></div><div>I have been t=
rying to define NTPv6 option to use with ISC-DHCPD6 daemon (4.4.1 running o=
n Ubuntu 22.04 server) as follows</div><div><br></div><div># ntp option 56<=
br>option space ntp code width 2 length width 2 hash size 2;<br>option ntp.=
address code 1 =3D array of ip6-address;<br>option opt56 code 56 =3D encaps=
ulate ntp;</div><div><br></div><div>and then use it in a subnet as follows<=
/div><div><br></div><div>shared-network enp7s0 {<br>=C2=A0 =C2=A0 authorita=
tive;<br>=C2=A0 =C2=A0 # deny bootp;<br>=C2=A0 =C2=A0 subnet6 fc00:6ce4:40:=
146::/64 {<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 pool6 {<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 # vendor-option-space ntp;<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 option ntp.address fc00:6ce4:40:146::1;<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 default-lease-time 600;<br>=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 min-lease-time 450;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 max-lease-time 900;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 allow all clients;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 range6 =
fc00:6ce4:40:146::10 fc00:6ce4:40:146::ffff;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 }<br>=C2=A0 =C2=A0 }<br>}</div><div><br></div><div>but no matter what I do=
, the ISC does not seem to include Option 56 in the Reply / Advertise messa=
ges, even though the client does request Option 56. I have spent probably 4=
8 hrs in total already, resulting in discovering that the only thing that s=
eems to be working is a brute force hex encoded string (example below)</div=
><div><br></div><div>option dhcp6.ntp-servers code 56 =3D string;<br>option=
 dhcp6.ntp-servers 00:01:00:10:20:01:0d:b8:0c:a2:00:02:00:00:00:00:00:00:00=
:01;</div><div><br></div><div>Is there any trick to forcing the ISC daemon =
to include the encapsulation option?</div><div><br></div><div>Thank you in =
advance <br></div><div><br></div><div>M<br> </div></div>

--000000000000699cd4060f3ce8e2--

--===============8148431457597796659==
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

--===============8148431457597796659==--