From nobody Sun Feb 23 16:56:11 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z194f6c8Dz5p4Nl; Sun, 23 Feb 2025 16:56:34 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from gid2.gid.co.uk (ns0.gid.co.uk [IPv6:2001:470:94de::240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gid2.gid.co.uk", Issuer "gid2.gid.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z194f2gfcz3ZwJ; Sun, 23 Feb 2025 16:56:34 +0000 (UTC) (envelope-from rb@gid.co.uk) Authentication-Results: mx1.freebsd.org; none Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by gid2.gid.co.uk (8.15.2/8.15.2) with ESMTP id 51NGuQ0g060112; Sun, 23 Feb 2025 16:56:26 GMT (envelope-from rb@gid.co.uk) Received: from smtpclient.apple (moriarty.gid.co.uk [194.32.164.17]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id 51NGuLH9093479; Sun, 23 Feb 2025 16:56:21 GMT (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\)) Subject: Re: rtadvd(8) How to IPv6 tokenize interface identifier From: rb@gid.co.uk In-Reply-To: <20250223144203.7f61d0bf@thor.sb211.local> Date: Sun, 23 Feb 2025 16:56:11 +0000 Cc: FreeBSD CURRENT , "freebsd-net@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <20250221075300.4466057d@thor.sb211.local> <2D84F83E-4548-40FA-B817-39703C670B43@gid.co.uk> <20250223144203.7f61d0bf@thor.sb211.local> To: A FreeBSD User X-Mailer: Apple Mail (2.3776.700.51.11.1) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4Z194f2gfcz3ZwJ X-Spamd-Bar: ---- Hi, > On 23 Feb 2025, at 13:52, A FreeBSD User = wrote: >=20 > Am Fri, 21 Feb 2025 10:44:12 +0000 > Bob Bishop schrieb: >=20 >> Hi, >>=20 >>> On 21 Feb 2025, at 06:52, A FreeBSD User = wrote: >>>=20 >>> Hello, >>>=20 >>> Linux (especially OpenWRT we use) knows about a concept named "IPv6 = tokenized interface >>> identifier". The concept is self explanatory, a interface/router = obtains a propagated >>> prefix and the concept allows the explicit definition of the host = portion. >>>=20 >>> I haven't managed to accomplish such a behaviour using FreeBSD's = rtadvd(8) daemon. I guess >>> this task is subject of and performed through the rtadvd.conf(5) = configuration file, but I >>> haven't managed yet to accomplish such a task (to speak simple: I'd = like to have a router >>> of a subnet always at IPv6 Network PREFIX:0:0:0:1). =20 >>=20 >> Isn=E2=80=99t sufficient just to give the router a static IPv6 = address? That=E2=80=99s what we do here. >=20 > Hello. >=20 > The router itself has on all inbound NICs static ULAs, ending as = desired on "fc:/7-PREFIX::1". > Using KAME dhcp6c, Ah. Nothing good will happen if you mix DHCP6 and SLAAC. > software from 2008(!), with a configuration obatined for delegating a > prefix, each NIC - except tun0 for whatever reason - gets a prefix, = the inbound NICs then seem > to get a EUI64 generated IPv6 (although I sepcified "privacy", but = this seems to be > ignored, sadly ...).=20 >=20 >>=20 >>> The only config tag I can imagine is responsible for what I'd like = to achive is the "addr" >>> tag mentioned in rtadvd.conf(5), but whatever I fill this tag with - = the desired effect is >>> never achived (i.e addr=3D"::0.0.0.1"). My "FreeBSD homebrewn" = router has several networks, >>> attached to vlan. Each interface is subject of an ULA prefix and an = IPv6 prefix provided >>> by our ISP. It is possible to pin the ULA toward the desired = address, like >>> addr=3D"fd50:c450::1", but then the ISP provided prefix seems not to = be set properly or is >>> completely absent. Omitting "addr=3D" provides the interface with = ULA prefix and ISP prefix >>> - but obviously with the randomly generated 64bit host portion. >>>=20 >>> Playing around with mutually suitable tags, like "pinfoflags", = "raflags" or "rtflags" and >>> having probed almost every possible combination (with or without = some sense), it seems >>> impossible to provide a) both ULA and ISP prefix pin the host = portion to a desired 64bit >>> address, like "PREFIX::1". >>>=20 >>> I do not exclude that I'm possibly incapable of comprehension the = manpage (the language is >>> and the deeper semantics seem then to be hidden for me). So, if = there is a clear >>> expalanation how to achive the desired, please point me towards it = (thanks in advance!). >>>=20 >>> Linux has this feature since a while and I can not believe that = FreeBSD lacks such a >>> feature. >>>=20 >>> Thank you very much in advance, >>>=20 >>> O. Hartmann >>>=20 >>>=20 >>> --=20 >>>=20 >>> A FreeBSD user =20 >>=20 >> -- >> Bob Bishop >> rb@gid.co.uk >>=20 >>=20 >>=20 >>=20 >=20 >=20 >=20 > --=20 >=20 > A FreeBSD user -- Bob Bishop t: +44 (0)118 940 1243 rb@gid.co.uk m: +44 (0)783 626 4518