Date: Wed, 21 May 2025 16:01:49 +0100 From: void <void@f-m.fm> To: freebsd-current@freebsd.org Subject: Re: HEADS UP: 15.0-CURRENT, =?utf-8?Q?chan?= =?utf-8?Q?ge_to_bridge=284=29_might_break_some_network_configurations_wit?= =?utf-8?B?aCDigJxJbnZhbGlkIGFyZ3VtZW504oCd?= Message-ID: <aC3q3Sj20Rcc49nW@int21h> In-Reply-To: <3647A8FC-FED1-4539-8BDE-CACCF6A5FC0A@FreeBSD.org> References: <aCsJDjfCNk5pA59c@ragweed.eden.le-fay.org> <aC3l356uZYcPDx_h@int21h> <3647A8FC-FED1-4539-8BDE-CACCF6A5FC0A@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Wed, May 21, 2025 at 04:44:46PM +0200, Kristof Provost wrote: >>[2] because here bge1 has an ip addigned to it and is a bridge member > >Yes, that is a problem. Assign REDACTED.REAL.IP to bridge1, not to bge1. Oof! Thank you for clarifying. I'm glad I asked. This bhyve host was set up following instructions from the bhyve section of the handbook. I've just checked and no mention is made of the new requirement in section 24.7.1 of the handbook at https://freebsd.org/handbook So, if a lot of people run bhyve guests as described then more people are going to be affected than one might initially presume. --help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aC3q3Sj20Rcc49nW>