From: Kristof Provost Date: Tue, 29 Jul 2025 13:30:50 +0200 Message-ID: In-Reply-To: References: <20250729093857.37832-1-kprovost@...2661...> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_0351E54B-0C07-43E9-AB3F-9A27BB03E041_=" Content-Transfer-Encoding: 8bit Subject: Re: [Openvpn-devel] [PATCH 1/2] dco-freebsd: pass address scope to the kernel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gert Doering Cc: openvpn-devel --=_MailMate_0351E54B-0C07-43E9-AB3F-9A27BB03E041_= Content-Type: text/plain; charset="utf-8"; format="flowed"; markup="markdown" Content-Transfer-Encoding: 8bit On 29 Jul 2025, at 13:07, Gert Doering wrote: > On Tue, Jul 29, 2025 at 12:55:29PM +0200, Kristof Provost via > Openvpn-devel wrote: >> This requires kernel side support: >> [https://reviews.freebsd.org/D51596](https://reviews.freebsd.org/D51596) > > I did not yet test it, but I assume that including scope-id in the > message to an older kernel will not break anything for non-LLA peers? > Correct. That’s why we’re using nvlists in the ioctl path. We can add fields without confusing either kernel or userspace. They’ll just be ignored. — Kristof --=_MailMate_0351E54B-0C07-43E9-AB3F-9A27BB03E041_= Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On 29 Jul 2025, at 13:07, Gert Doering wrote:

On Tue, Jul 29, 2025 at 12:55:29PM +0200, Kristof Provost v= ia Openvpn-devel wrote:

This requires kernel side support: https://reviews.freebsd.org/D51596

I did not yet test it, but I assume that including scope-id= in the
message to an older kernel will not break anything for non-LLA peers?

Correct. That=E2=80=99s why we=E2=80=99re using nvlists in = the ioctl path. We can add fields without confusing either kernel or usersp= ace. They=E2=80=99ll just be ignored.

=E2=80=94
Kristof

--=_MailMate_0351E54B-0C07-43E9-AB3F-9A27BB03E041_=--