Date: Thu, 24 Jul 2025 16:41:12 +0100 From: void <void@f-m.fm> To: freebsd-current <freebsd-current@freebsd.org> Subject: Re: ifconfig_bxe0_ipv6="inet6 accept_rtadv" seems to break bridging Message-ID: <756d400d-fa0f-45ea-ba24-235234ee41ff@app.fastmail.com> In-Reply-To: <aIIwQq2GQyiAoaTp@freefall.freebsd.org> References: <aIIuGOc9-hdvUyFU@int21h> <aIIwQq2GQyiAoaTp@freefall.freebsd.org>
index | next in thread | previous in thread | raw e-mail
Hi, On Thu, 24 Jul 2025, at 14:08, Lexi Winter wrote: > you should set accept_rtadvd on the bridge interface, not the member > interface. setting it on the member interface will try to assign the > SLAAC address to the member, which is not allowed. > > you may also need to set some other inet6 flags, since for historical > reasons these are disabled on bridges by default: > > ifconfig_bridge0_ipv6="inet6 -ifdisabled auto_linklocal accept_rtadv" Apologies in advance if these questions seem dumb. I don't know much about bridging and cannot, in what I've searched in so far, find worked examples close enough to what's needed.[1] OK. Now the rc.conf looks like this: cloned_interfaces="bridge0 tap0" ifconfig_bxe0="up" ifconfig_bridge0="203.0.113.2/24 addm bxe0 addm tap0" defaultrouter="203.0.113.1" ifconfig_bridge0_ipv6="inet6 -ifdisabled auto_linklocal accept_rtadv" Rebooted, same result - ipv4 has no route, ipv6 works. Have I got the syntax wrong, or do these lines need to be in a different order? [1] the server gets 203.0.113.2 and ipv6 address, the tap gets 203.0.113.3/24 (configured internally in the vm) i.e routable ipv4 configured manually, slaac autoconfig for everything. Work so far is just on the server. --help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?756d400d-fa0f-45ea-ba24-235234ee41ff>