From nobody Wed May 21 14:40:31 2025 X-Original-To: net@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 4b2Yxd2HmRz5w1TT; Wed, 21 May 2025 14:40:37 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fhigh-a1-smtp.messagingengine.com (fhigh-a1-smtp.messagingengine.com [103.168.172.152]) (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 4b2Yxb2CzHz3f8J; Wed, 21 May 2025 14:40:35 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=mkjSsRdi; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=sWyp2wWM; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.152 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from phl-compute-12.internal (phl-compute-12.phl.internal [10.202.2.52]) by mailfhigh.phl.internal (Postfix) with ESMTP id 0323A114017F; Wed, 21 May 2025 10:40:34 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-12.internal (MEProxy); Wed, 21 May 2025 10:40:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc:cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1747838433; x=1747924833; bh=4o2529X8Lu rALBQdE5/PV1xu20kYxjPYAGBzIXIVVbE=; b=mkjSsRdioBv8iulFa9IdN5UIGT HwfC5Y89SOAFHsXjVl9/eYO+qsnwshP+slrU/DKw0c+URn1unfgMmAoXVHijUP5H PCRiV73inNXuLI5d2eIvpJKY5RcQ5ciZlwcUI4ts5bq9Y5yf0LDQEiHII/iDiTjq GyxX7WPzwBU1ovM8YqdjDhpk3j35ywBfbGhFsF1DiQeHWrqc2dr9ap7acjj5yGSj 6Tg2LFrCQkQFfenXrvDdOax3w+bMfCM92NV1DqDrIdphfsSlEvRbnMsIROIzPR6a 9pQhEeY9oy+dgR9S7Qmje7RJ0SSqutEdSO491XDvy3G3MUsESB6VdjERHIIA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1747838433; x=1747924833; bh=4o2529X8LurALBQdE5/PV1xu20kYxjPYAGB zIXIVVbE=; b=sWyp2wWMl79NqEQtbMhKYoBU7qxnS6ZyXLfaxQB9U0n2VG9xLnJ E+hE0OHZKz/7LX9G/UFh86JpCncw/UcOSskg816t6VsIs4Qvq8bY6OwNUpduYTsv 65Ehzp1Gse4yk+ZTtK/uRm3fkoA6IKINmaDK8R26dOHyr/M40/l3aoxWOl6zqrjf meOHBLu9GLtfojFhHlwuNks9k/qhLetXA2qZuPlbsIBbGzMNWOYj8NDEayM9jnIC 9ndtiYdbGwYLQgt9bkWS30Qc2DbtIYi5oHw9cZHnrtKr6o/nsXSSrBY6kpXcIvVQ /6/MXOet8nvtVz+ww659ayk59I7+0YHxTgg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtddtgdeffeehucdltddurdegfedvrddttd dmucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgf nhhsuhgsshgtrhhisggvpdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttd enucenucfjughrpeffhffvvefukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpehv ohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrghtthgvrhhnpeeggfehhfejje ekteeufeehfefhgeejgfeliedvhedvffffhffgiedtvddtgfehueenucffohhmrghinhep fhhrvggvsghsugdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehvohhiugesfhdqmhdrfhhmpdhnsggprhgtphhtthhopeefpdhmohgu vgepshhmthhpohhuthdprhgtphhtthhopehfrhgvvggsshguqdhnvghtsehfrhgvvggssh gurdhorhhgpdhrtghpthhtoheptghurhhrvghnthesfhhrvggvsghsugdrohhrghdprhgt phhtthhopehnvghtsehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 21 May 2025 10:40:33 -0400 (EDT) Date: Wed, 21 May 2025 15:40:31 +0100 From: void To: freebsd-net@freebsd.org Cc: current@freebsd.org, net@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: References: List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4b2Yxb2CzHz3f8J X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.92 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.924]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[103.168.172.152:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.152:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; MLMMJ_DEST(0.00)[current@freebsd.org,freebsd-net@freebsd.org,net@freebsd.org]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCPT_COUNT_THREE(0.00)[3]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] On Mon, May 19, 2025 at 11:33:50AM +0100, Lexi Winter wrote: >although it's possible everyone who is affected by this is already aware >of the change, i thought i should send a heads up anyway, if only to >have a single place to discuss this (since there was quite a lot of >discussion). > >in short, following this commit... > >b61850c4e6f "bridge(4): default net.link.bridge.member_ifaddrs to false" >https://cgit.freebsd.org/src/commit/?id=b61850c4e6f6b0f21b36da7238db969d9090309e > >...it is now impossible to use a network interface which has an IP >address assigned to it as a bridge member, or to configure an IP >address on an interface which is a member of a bridge. Hi, for the sake of clarity, when you say "IP addresses assigned to it as a bridge member", do you mean assigned via eg rc.conf on the host, or assigned, for example within a VM, or assigned within a bridge statement? [1] I have a machine with 2x NICs with static ips assigned in the usual way in rc.conf. They are also bridge members (they have to be otherwise the tap interfaces on the bhyve VMs wouldn't work) Within each vm the interfaces are assigned either static or dynamic IPs. I don't use vm-bhyve. Do I need to worry? [2] [1] example - /etc/rc.conf snippet on the bhyve host ifconfig_bge1="inet REDACTED.REAL.IP netmask 255.255.255.248 mtu 1500 media 1000baseT mediaopt full-duplex,master" defaultrouter="REDACTED.REAL.GATEWAY" ifconfig_bge1_ipv6="inet6 accept_rtadv" # # ifconfig_bridge1="addm bge1 addm tap10 addm tap11 addm tap12 \ addm tap13 addm tap14 addm tap15 addm tap16 addm tap17 addm tap18 addm tap19" # [2] because here bge1 has an ip addigned to it and is a bridge member --