From nobody Mon May 19 10:33:50 2025 X-Original-To: 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 4b1DYx2GCnz5wttX; Mon, 19 May 2025 10:33:57 +0000 (UTC) (envelope-from ivy@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4b1DYx05CVz3knf; Mon, 19 May 2025 10:33:57 +0000 (UTC) (envelope-from ivy@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1747650837; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=ALZXURuzCfkXuKe/Mi1c1Y32GE+GX9PjjjoiakLpoKw=; b=XVAcWNvR6XuR4K/lais4fNfEAm9krB/sjqaPqG4qFxTeHdO8KYezvZSh5Uq/vf8GVQoK9M fANyGdofcCF9TzGX3eqyXlf+cjmvcJQTx0ItbeyFNxmofhszTZ1RiAgqdBZu7OinCDmR5g fcvPZS3bVc2tdZqtuz0VuVe0BCi+Bf55AStl+GCdyy2+Al+BL7MOwJpH9sgSz48dCtd6nw npw0rRuUcV4KUyDriuniGhRMyMiMSOe3CwPm1r87ebt7zRhFSgL694MnqhW6xdZRPNupDw lAGCqjGkbogffJF11DLUy0gmWbk5OoYpMcC27raJj4ZeR98d2X5sd4GnB2gO0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1747650837; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=ALZXURuzCfkXuKe/Mi1c1Y32GE+GX9PjjjoiakLpoKw=; b=Y9+UCri35+pBRIs7N6yWJjOPOD0Ak6iALN+q8BokooI5OzzDGc/it+QDanRhzYJqOmPQxi s3Bx4o+35co9I4aVDPxrAWmyb/4kCSF9Jp0n+imAlCDMyUY8Q+TtDaxc5wruAQj6LRP5fq KIQHLLAb7pcnTSYgvT3X9O+XjXGilDneYPg5/KzM64Oq+xhCIEdNI3XNq5uDf3freaKcEc Avjm2ZfshjOLFPDzYib2rF/jwYW/I+JQZbujypuFgsdi5M3djH8NqUMm6e9Jare0pIpnst dj5qFZMvsecfHwobdYI51Ba4e9ERzvB472MwFwLpyGJMNX9GLR394N4jivJjKA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1747650837; a=rsa-sha256; cv=none; b=XF2s5bNaPdHNvdjQWdBlpS6MomEDVubOFjCwXliPkdv6l5fS6zlAuTsAmIuv2KIi9wEUCi 6CZrIp+bpLRBfl7AXvVPUW4aEUVmBM8TUP6HGfEA/lWRxbc94ZjGvtt+y3uutX8kNQ/gVP Qrtho+bdzNLhFURgjXLO2ACe7SdRtBWowW31dKGsFH5Scw0cdxa+wfjZiHaNqHbEfQ6452 IydM1+ngY0R30e7+YE8b5aWi2ZR2Rfn4QQQMgbuqrH4aiUDtwmyvFEUV/ox/ZQJFLQ9ytP UPEmBRsWJblRAzWV4gq4rOhamDaEK/8TpApKN8p+kJesyQ9ENosnmhSEHJgFLQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from ragweed.eden.le-fay.org (ragweed.eden.le-fay.org [IPv6:2001:8b0:aab5:c401:1::1]) (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) (Authenticated sender: ivy/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4b1DYw4d9Tz9jh; Mon, 19 May 2025 10:33:56 +0000 (UTC) (envelope-from ivy@FreeBSD.org) Date: Mon, 19 May 2025 11:33:50 +0100 From: Lexi Winter To: current@freebsd.org, net@freebsd.org Subject: HEADS UP: 15.0-CURRENT, change =?utf-8?Q?t?= =?utf-8?Q?o_bridge=284=29_might_break_some_network_configurations_with_?= =?utf-8?B?4oCcSW52YWxpZCBhcmd1bWVudOKAnQ==?= Message-ID: Mail-Followup-To: current@freebsd.org, net@freebsd.org 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 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="snmROKrOoOnHE87x" Content-Disposition: inline --snmROKrOoOnHE87x Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hello, 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. the immediate, "oh shit, my network is broken" fix for this issue is to set the sysctl net.link.bridge.member_ifaddrs=1. this will restore the previous behaviour of bridge(4). however, the preferred fix is that if you are doing something like this in /etc/rc.conf: cloned_interfaces="bridge0" ifconfig_ix0="1.1.1.1/24" ifconfig_bridge0="addm ix0" you should do this instead: cloned_interfaces="bridge0" ifconfig_ix0="up" ifconfig_bridge0"1.1.1.1/24 addm ix0" in other words, instead of assigning the IP address to the member interface, assign it to the bridge instead. i am aware that there are some configurations which currently cannot be done this way. in that case, please set member_ifaddrs=1 and i hope to have resolved all of these cases prior to 16.0-RELEASE, at which point i intend to remove the member_ifaddrs sysctl. i do *not* intend to revert this commit, but i *do* want to work with people who are negatively affected by this change to address their use-case prior to the removal of the aforementioned sysctl. specific known issues: - ifconfig_bridge0="SYNCDHCP" may be broken, in which case try "DHCP" instead. - automatic dhclient invocation on a bridge member via devd when the link comes up is broken. in both cases, setting member_ifaddrs=1 will restore the previous behaviour. again, i intend to fix or provide alternatives for all known breakages caused by this commit. --snmROKrOoOnHE87x Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaCsJDQAKCRD1nT63mIK/ YOpTAQDdeW8qdnlo7ZXK1+XtWhB7VVUjwO3WiMxv9r2CPj1KGwD+PUh1n9jspK2p x1wU2HNT5zqMRAtdA7GXg5tEuPy1Ng0= =AcAA -----END PGP SIGNATURE----- --snmROKrOoOnHE87x--