From nobody Sun Feb 23 13:52:44 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 4Z15196kpCz5nm8V; Sun, 23 Feb 2025 13:53:17 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [85.220.129.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z15185sWpz3FHK; Sun, 23 Feb 2025 13:53:16 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=tGIrO7CQ; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 85.220.129.31 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de Received: from hub1.goneo.de (hub1.goneo.de [IPv6:2001:1640:5::8:52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id 16883240F06; Sun, 23 Feb 2025 14:53:14 +0100 (CET) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id 83854240370; Sun, 23 Feb 2025 14:53:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1740318792; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=q4F1ELXj9KfAp0UMRWW8vnSOY44mxTqTouKdq7zU5UA=; b=tGIrO7CQoseewEWiMe3qiQkX3Y0vPIszTnIXT5a9Lp158g+LFo7ECT+Pq2lcpSJARbYH4O sdui1mfvzo98gatNEZa3vIXrXIJObj+BA/yzxOnncMX1ITQhYtHjOaSHSajTBHwA3auc6b n7jkQ1JEt0JhxEs8y2OJ6EQZQqBS0FdEPYEcC+LShyBoSpM1vtJORk8n9fFaFMCI9soTeG F0pO0YpFvzU9WDVneYxFFgD3to5mt24kExE3JMGyPj4MOB1QvaRImnLAfWkaUitGCXvOA2 HVOn0kqDee54F6iwrswplVoz1ZMGVrPUpdLTPkpKy6bkYIAbRMoYXQlCuknVPg== Received: from thor.sb211.local (dynamic-2a02-3100-1a5d-2802-751a-9ae2-1d14-0faa.310.pool.telefonica.de [IPv6:2a02:3100:1a5d:2802:751a:9ae2:1d14:faa]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 229C42402ED; Sun, 23 Feb 2025 14:53:12 +0100 (CET) Date: Sun, 23 Feb 2025 14:52:44 +0100 From: A FreeBSD User To: Bob Bishop Cc: FreeBSD CURRENT , "freebsd-net@freebsd.org" Subject: Re: rtadvd(8) How to IPv6 tokenize interface identifier Message-ID: <20250223144203.7f61d0bf@thor.sb211.local> In-Reply-To: <2D84F83E-4548-40FA-B817-39703C670B43@gid.co.uk> References: <20250221075300.4466057d@thor.sb211.local> <2D84F83E-4548-40FA-B817-39703C670B43@gid.co.uk> 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 Content-Type: multipart/signed; boundary="Sig_/vXO=ctu1Xv7nwtnQZNzQupa"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: 3ad66d X-Rspamd-UID: 01953f X-Spamd-Result: default: False [-1.51 / 15.00]; SIGNED_PGP(-2.00)[]; RBL_SENDERSCORE_REPUT_9(-1.00)[85.220.129.31:from]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; NEURAL_SPAM_LONG(0.99)[0.995]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; R_SPF_ALLOW(-0.20)[+ip4:85.220.129.0/25]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; NEURAL_SPAM_SHORT(0.20)[0.200]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.31:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[85.220.129.31:from]; DMARC_NA(0.00)[walstatt-de.de]; RCVD_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; MLMMJ_DEST(0.00)[freebsd-current@FreeBSD.org,freebsd-net@FreeBSD.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DKIM_TRACE(0.00)[walstatt-de.de:+]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4Z15185sWpz3FHK X-Spamd-Bar: - --Sig_/vXO=ctu1Xv7nwtnQZNzQupa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Fri, 21 Feb 2025 10:44:12 +0000 Bob Bishop schrieb: > 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 tok= enized interface > > identifier". The concept is self explanatory, a interface/router obtain= s a propagated > > prefix and the concept allows the explicit definition of the host porti= on. > >=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) config= uration file, but I > > haven't managed yet to accomplish such a task (to speak simple: I'd lik= e 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? T= hat=E2=80=99s what we do here. Hello. The router itself has on all inbound NICs static ULAs, ending as desired on= "fc:/7-PREFIX::1". Using KAME dhcp6c, software from 2008(!), with a configuration obatined for= delegating a prefix, each NIC - except tun0 for whatever reason - gets a prefix, the inb= ound NICs then seem to get a EUI64 generated IPv6 (although I sepcified "privacy", but this see= ms to be ignored, sadly ...).=20 =20 >=20 > > The only config tag I can imagine is responsible for what I'd like to a= chive is the "addr" > > tag mentioned in rtadvd.conf(5), but whatever I fill this tag with - th= e desired effect is > > never achived (i.e addr=3D"::0.0.0.1"). My "FreeBSD homebrewn" router h= as several networks, > > attached to vlan. Each interface is subject of an ULA prefix and an IPv= 6 prefix provided > > by our ISP. It is possible to pin the ULA toward the desired address, l= ike > > 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 p= refix 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 s= ense), it seems > > impossible to provide a) both ULA and ISP prefix pin the host portion t= o a desired 64bit > > address, like "PREFIX::1". > >=20 > > I do not exclude that I'm possibly incapable of comprehension the manpa= ge (the language is > > and the deeper semantics seem then to be hidden for me). So, if there i= s a clear > > expalanation how to achive the desired, please point me towards it (tha= nks 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 A FreeBSD user --Sig_/vXO=ctu1Xv7nwtnQZNzQupa Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCZ7soRwAKCRCxzvs8Oqok rxDoAP0YSMsesSBXe+1o0NYxpLWXqSv7GOX992f+hO7mPWLRGQEAgrw6+F5PH+cP Z7xwzuKqcUfL7qWlOgW1ZVwy7jKz7QY= =201v -----END PGP SIGNATURE----- --Sig_/vXO=ctu1Xv7nwtnQZNzQupa--