Date: Thu, 24 Jul 2025 23:41:17 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@freebsd.org>, void <void@f-m.fm>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: ifconfig_bxe0_ipv6="inet6 accept_rtadv" seems to break bridging Message-ID: <21cec060-6e1b-4ab3-b0ad-b67c5a7fc288@quip.cz> In-Reply-To: <aIKVMTT5-VL-YkXW@freefall.freebsd.org> References: <aIIuGOc9-hdvUyFU@int21h> <aIIwQq2GQyiAoaTp@freefall.freebsd.org> <756d400d-fa0f-45ea-ba24-235234ee41ff@app.fastmail.com> <868qkd9wkf.fsf@ltc.des.dev> <aIKVMTT5-VL-YkXW@freefall.freebsd.org>
index | next in thread | previous in thread | raw e-mail
On 24/07/2025 22:18, Lexi Winter wrote: > Dag-Erling Smørgrav: >> void <void@f-m.fm> writes: >>> ifconfig_bridge0="203.0.113.2/24 addm bxe0 addm tap0" >> >> missing `inet` here. > > not required. however, i think it should be. > > the problem is if we start requiring this it's going to break > *everyone's* network configuration and i can't come up with a > better reason than "it's neater this way". Well, I've never used or seen the ifconfig_XXX variable with IP in rc.conf without inet. So if somebody has it without it, it's probably wrong configuration. Similar to what has "changed" recently with IP on bridge members instead of IP on bridge. Kind regards Miroslav Lachmanhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21cec060-6e1b-4ab3-b0ad-b67c5a7fc288>