Date: Tue, 30 Jul 2024 09:10:27 +0900 (JST) From: moto kawasaki <moto@kawasaki3.org> To: roy@marples.name Cc: cross+freebsd@distal.com, freebsd-net@freebsd.org Subject: Re: =?iso-8859-1?Q?=A0DHCPv6?= IA_PD - how-to Message-ID: <20240730.091027.1008656135460861216.moto@kawasaki3.org> In-Reply-To: <190fdf3e353.11351bb5e292296.3216692081725884177@marples.name> References: <050440F8-B3D8-4B2C-85BD-D5C09C303037@distal.com> <20240727.122108.862717899466090274.moto@kawasaki3.org> <190fdf3e353.11351bb5e292296.3216692081725884177@marples.name>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Roy, Thank you very much for the configuration example with dhcpcd! Also I didn't know delayed auth had been obsoleted, thanks for letting me to notice. I'll try dhcpcd instead of dhcp6c. Best Regards, -- moto kawasaki <moto@kawasaki3.org> +81-90-2464-8454 on Mon, 29 Jul 2024 11:05:37 +0100, Roy Marples <roy@marples.name> wrote: > For dhcpcd you would do this: > > interface vtnet0 > ia_pd 3 vtnet1/11 vtnet2/12 > option domain_name_servers, domain_name, ntp_servers > authproto delayed > authtoken 1 "example.org" forever "JTY0XXXXXXXXXXXXXXX==" > > > But please note that delayed authentication has now been obsoleted: > https://datatracker.ietf.org/doc/html/rfc8415#section-25 > While dhcpcd supports it to some extend, it's not widely tested and could be broken in any given release as I don't have a means of testing it right now. > > The only real authentication support that is in the RFC's is the reconfigure key. > https://datatracker.ietf.org/doc/html/rfc8415#section-20.4 > > Roy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240730.091027.1008656135460861216.moto>