From nobody Sun May 18 19:24:17 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 4b0rNX5HQRz5whSS for ; Sun, 18 May 2025 19:24:28 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (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 (2048 bits) client-digest SHA256) (Client CN "plan-b.pwste.edu.pl", Issuer "GEANT OV RSA CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4b0rNX1fcWz3fFp for ; Sun, 18 May 2025 19:24:28 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Authentication-Results: mx1.freebsd.org; none Received: from [192.168.7.70] (dom.potoki.eu [62.133.140.50]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.18.1/8.17.2) with ESMTPSA id 54IJOJOt021020 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Sun, 18 May 2025 21:24:19 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1747596259; bh=alsUvnOcMHQ33J7cLvs4ZZKpx277XjnNegyApcLhK48=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=CvXcnWCL5Xr2ua8ijD4itI9nlbAp7KBSe2HjwlWwq0EW2LvrrV2fBmj2frAIGc6zB i8NU9ybKX8qTWMhQCfv6dnn5tMdq3/8t2QNWxgHGocBTRftKF8XAO00bOAZGVTfjlh IVenjVT0siH84ns2Yyr2KQAmDmJq3IUnsFuuKVr2lIPuqsZxQ/RQaKoMgrmuJAiIvd 8G8Cn2mjm7BdcYJoh+LA0PipvsZPUlRjwTAW+gpY2XnAmfIYumT7xtUPtNCOPjUZos DDhufyK0EbKIj/O+9Hqkido+6quHDfCiFRR4BiCy7LB2jEFy1aq/ZB/Y6RaUXGYnq8 BrOlhIHrY0x/g== X-Authentication-Warning: plan-b.pwste.edu.pl: Host dom.potoki.eu [62.133.140.50] claimed to be [192.168.7.70] Message-ID: <310d460a-d372-47c8-8275-2908bb8417ad@plan-b.pwste.edu.pl> Date: Sun, 18 May 2025 21:24:17 +0200 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 User-Agent: Mozilla Thunderbird Subject: Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument To: Alexander Leidinger , A FreeBSD User , rgrimes@freebsd.org Cc: FreeBSD CURRENT References: <20250518180658.2e58d55a@thor.sb211.local> <192c8e37-4a85-4916-9986-0a556333a527@plan-b.pwste.edu.pl> <20250518182404.3a760da9@thor.sb211.local> <1ca30cdfb783848eafce24b77f10c0a5@Leidinger.net> Content-Language: en-US From: Marek Zarychta Autocrypt: addr=zarychtam@plan-b.pwste.edu.pl; keydata= xsBNBFfi3cMBCADLecMTFXad4uDXqv3eRuB4qJJ8G9tzzFezeRnnwxOsPdytW5ES2z1ibSrR IsiImx6+PTqrAmXpTInxAi7yiZGdSiONRI4CCxKY9d1YFiNYT/2WyNXCekm9x29YeIU7x0JB Llbz0f/9HC+styBIu2H+PY/X98Clzm110CS+n/b9l1AtiGxTiVFj7/uavYAKxH6LNWnbkuc5 v8EVNc7NkEcl5h7Z9X5NEtzDxTOiBIFQ/kOT7LAtkYUPo1lqLeOM2DtWSXTXQgXl0zJI4iP1 OAu4qQYm2nXwq4b2AH9peknelvnt1mpfgDCGSKnhc26q6ibTfMwydp+tvUtQIQYpA6b9ABEB AAHNN01hcmVrIFphcnljaHRhIChQbGFuLWIpIDx6YXJ5Y2h0YW1AcGxhbi1iLnB3c3RlLmVk dS5wbD7CwHcEEwEIACEFAlfi4LkCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQHZW8 vIFppoJXdgf8D9X3VRFSNaR9lthSx/+uqas17J3FJKBo1xMQsC2a+44vzNvYJSuPGLLJ+LW2 HPVazjP/BWZJbxOYpliY4zxNRU0YCp0BLIVLibc//yax+mE42FND/+NiIZhqJscl6MLPrSwo sIwXec4XYkldkyqW/xBbBYXoIkBqdKB9j5j42Npy1IV/RizOSdmvTWY27ir8e/yGMR1RLr4F 8P5K3OWTdlGy2H2F/3J8bIPBLG6FpaIyLQw4dHSx8V02PYqDxK1cNo2kAOnU8PnZL/AGuMOH iv3MN1VYL8ehcmpBBsrZGebQJxrjY2/5IaTSgp9xHYT70kshuU6Qb97vk1mOjNZxgc7ATQRX 4t3DAQgA10h6RCXuBLMHxq5B8X/ZIlj9sgLoeyfRdDZEc9rT2KUeUJVHDsbvOFf4/7F1ovWY hJbA6GK/LUZeHHTjnbZcH1uDYQeHly4UOLxeEvhGoz4JhS2C7JzN/uRnwbdOAUbJr8rUj/IY a7gk906rktsc/Ldrxrxh7O6WO0JCh2XO/p4pDfEwwB37g4xHprSab28ECYJ9JMbtA8Sy4M55 g3+GQ28FvSlGnx48OoGXU2BZdc1vZKSQmNOlikB+9/hDX8zdYWVfDaX1TLQ8Ib4+xTUmapza mV/bxIsaZRBw+jFjLQHhTbIMfPEU+4mxFDvTdbKPruKPqVf1ydgMnPZWngowdwARAQABwsBf BBgBCAAJBQJX4t3DAhsMAAoJEB2VvLyBaaaC6qkIAJs9sDPqrqW0bYoRfzY6XjDWQ59p9tJi v8aogxacQNCfAu+WkJ8PNVUtC1dlVcG5NnZ80gXzd1rc8ueIvXlvdanUt/jZd8jbb3gaDbK3 wh1yMCGBl/1fOJTyEGYv1CRojv97KK89KP5+r8x1P1iHcSrunlDNqGxTMydNCwBH23QcOM+m u4spKnJ/s0VRBkw3xoKBZfZza6fTQ4gTpAipjyk7ldOGBV+PvkKATdhK2yLwuWXhKbg/GRlD 1r5P0gxzSqfV4My+KJuc2EDcrqp1y0wOpE1m9iZqCcd0fup5f7HDsYlLWshr7NQl28f6+fQb sylq/j672BHXsdeqf/Ip9V4= In-Reply-To: <1ca30cdfb783848eafce24b77f10c0a5@Leidinger.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4b0rNX1fcWz3fFp 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:206006, ipnet:2001:678:618::/48, country:PL] X-Spamd-Bar: ---- W dniu 18.05.2025 o 19:48, Alexander Leidinger pisze: > Am 2025-05-18 18:23, schrieb A FreeBSD User: >> Am Tage des Herren Sun, 18 May 2025 18:16:43 +0200 >> Marek Zarychta schrieb: >> >>> W dniu 18.05.2025 o 18:06, A FreeBSD User pisze: >>> > Hello, >>> > >>> > running recent CURRENT (FreeBSD 15.0-CURRENT #68 >>> main-n277334-d9900b9ea2b2: Sun May 18 >>> > 16:51:02 CEST 2025), I ran into the following problem: >>> > Can not add interfaces anymore to a bridge device. >>> > Neither existing physical devices, nor epair devices created >>> during setup of jails - with >>> > the result of no jails availabel and/or no bridge working. >>> > >>> > A more amusing part of this story is: I ran almost two identical >>> boxes, based upon elderly >>> > IvyBridge CPUs, both on outdated ASrock Z77 Pro mainboards. One >>> machine, the >>> > now-failing-one, has moved to AMD Ryzen 9700X based box based on >>> ASrock B850 mainboard - >>> > just for the record, if this is of importance or interest. >>> > >>> > On both systems I use custom kernels, mostly disabling unused >>> devices. Having an ABI issue >>> > in mind, I recompiled the whole world/kernel on the system with >>> AMD CPU, but the issue is >>> > the still persistent. >>> > >>> > A real hardware problem or just a coincidence with faulty code? >>> > >>> > Thanks for helping, >>> > >>> > O. Hartmann >>> > >>> > >>> Hello Oliver, >>> >>> please follow this commit: >>> >>> https://github.com/freebsd/freebsd-src/commit/b61850c4e6f6b0f21b36da7238db969d9090309e >>> >>> >>> and this thread: >>> >>> https://lists.freebsd.org/archives/freebsd-current/2025-May/007602.html >>> >>> TL;DR: set net.link.bridge.member_ifaddrs=1 (the earlier, the better, >>> loader.conf prefered) and before FreeBSD 16.0-RELEASE (still plenty of >>> time), either remove addresses the bridge members, or consider >>> migration >>> to different bridge (Netmap ?!) or consider migration to different OS. >>> >>> Cheers >>> >>> Marek >>> >>> >> >> Hello, >> >> sorry for the noise. >> >> Just after sending, I read the thread started by Cy Schubert "epair(4)". >> Adding >> net.link.bridge.member_ifaddrs=1 >> >> solves the problem for me on the host in question! > > You want to make it work without this. Short: use the IP on the bridge > itself, not in the member IF. > > Bye, > Alexander. > I'm not sure we should be dictating to Oliver what he must do. There are multiple possible solutions. One could, for example, use ng_bridge(4), or take yet another direction entirely. Users should be free to experiment and work flexibly with the operating system. Forcing everyone to move all their addresses to the logical bridge(4) interface seems like it narrows the range of valid deployment scenarios for bridge(4) That said, is the fact that a few users are experiencing issues with multicast between interfaces connected to a bridge - or that they struggle to migrate addresses onto the bridge interface - really a sufficient reason to prohibit everyone from assigning addresses to bridge members? Multicast does work. It just doesn’t work between bridge members. Maybe someone will fix that someday. And even if they don’t, it’s been this way from the start, so probably people have learned to live with it. Back to Cy Schubert’s thread about epair(4), which touches on this issue: what's striking is that this change doesn’t just shoot users in the foot, it shoots and surprises committers as well. Committers who, well, will grit their teeth and defend the change regardless. Please don’t take this as a defense of the old configuration style. As I said before, if necessary I’ll just migrate to ng_bridge(4) or even switch to another OS. Netmap would likely be overkill for a laptop running a bridge temporarily. I do miss people like the late Mike Karels, who would have made a clear and confident decision about how this should be handled. Where is the Janitor? Mr Grimes -  where are you? As a user with 30 years of experience with this OS, allow me to ask: who’s actually in charge of all this now? -- Marek Zarychta