From nobody Thu May 22 17:40:52 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 4b3FvX549Mz5wxbm for ; Thu, 22 May 2025 17:41:12 +0000 (UTC) (envelope-from pmh@hausen.com) Received: from mail2.pluspunkthosting.de (mail2.pluspunkthosting.de [217.29.33.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4b3FvX08r1z49pd for ; Thu, 22 May 2025 17:41:11 +0000 (UTC) (envelope-from pmh@hausen.com) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (87.138.185.145) by mail2.pluspunkthosting.de (Axigen) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA id 05A9EC; Thu, 22 May 2025 19:41:02 +0200 From: "Patrick M. Hausen" Message-Id: <8DCF0DAB-5EE5-4FEF-8CCC-1D7AF971BA8C@hausen.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_E1D06D2C-7E9F-4CC8-9372-6E6804F1AB48" 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 \(3826.600.51.1.1\)) Subject: Re: epair(4) Date: Thu, 22 May 2025 19:40:52 +0200 In-Reply-To: Cc: freebsd-current@freebsd.org To: void References: <20250515162552.9209B20E@slippy.cwsent.com> <20250515185919.87008219@slippy.cwsent.com> <45d0f49d-229b-46b4-af95-6e8c4c856661@plan-b.pwste.edu.pl> <932111f8-f5ca-46d1-9f66-983f80f6116b@protected-networks.net> X-Mailer: Apple Mail (2.3826.600.51.1.1) X-Rspamd-Queue-Id: 4b3FvX08r1z49pd 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:16188, ipnet:217.29.32.0/20, country:DE] X-Spamd-Bar: ---- --Apple-Mail=_E1D06D2C-7E9F-4CC8-9372-6E6804F1AB48 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all, > Am 22.05.2025 um 02:14 schrieb void : >=20 > On Fri, May 16, 2025 at 09:21:29PM +0100, Lexi Winter wrote: >=20 >> i am not sure about this. i admit i have not done a survey :-) = however, >> i believe most people using jails or bhyve are not affected. the >> Handbook is clear about the correct way to configure this[0], so = people >> who followed the handbook to configure their jails or bhyve VMs = should >> not run into this problem. >=20 > Your belief that most people using bhyve and jails would be unaffected > is, I think, misplaced. The handbook has only been clear about > the "correct way to configure" this since around the middle of last = year [1] > [...] The handbook has always been clear about the only correct way to = configure a bridge and member interfaces since the introduction of if_bridge(4) = and the removal of the previous bridge(4) in 2007: = https://svnweb.freebsd.org/doc/head/en_US.ISO8859-1/books/handbook/advance= d-networking/chapter.xml?revision=3D30565&view=3Dmarkup If the bridge host needs an IP address then the correct place to set this is on the bridge interface itself rather than one of the member interfaces. This can be set statically or via DHCP. Kind regards, Patrick --Apple-Mail=_E1D06D2C-7E9F-4CC8-9372-6E6804F1AB48 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi all,

Am 22.05.2025 um 02:14 schrieb void = <void@f-m.fm>:

On Fri, May 16, 2025 at = 09:21:29PM +0100, Lexi Winter wrote:

i = am not sure about this.  i admit i have not done a survey :-) = however,
i believe most people using jails or bhyve are not affected. =  the
Handbook is clear about the correct way to configure = this[0], so people
who followed the handbook to configure their jails = or bhyve VMs should
not run into this = problem.

Your belief that most people using bhyve = and jails would be unaffected
is, I think, misplaced. The handbook = has only been clear about
the "correct way to configure" this since = around the middle of last year [1]
[...]

T= he handbook has always been clear about the only correct way to = configure
a bridge and member interfaces since the = introduction of if_bridge(4) and the
removal of the previous = bridge(4) in 2007:


<= /div>
= If the bridge host needs an IP address then the = correct
        place to set this is on = the bridge interface itself rather
        = than one of the member interfaces.  This can be set = statically
        or via = DHCP.

Kind = regards,
Patrick


= --Apple-Mail=_E1D06D2C-7E9F-4CC8-9372-6E6804F1AB48--