Date: Sun, 18 May 2025 18:23:37 +0200 From: A FreeBSD User <freebsd@walstatt-de.de> To: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Message-ID: <20250518182404.3a760da9@thor.sb211.local> In-Reply-To: <192c8e37-4a85-4916-9986-0a556333a527@plan-b.pwste.edu.pl> References: <20250518180658.2e58d55a@thor.sb211.local> <192c8e37-4a85-4916-9986-0a556333a527@plan-b.pwste.edu.pl>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Am Tage des Herren Sun, 18 May 2025 18:16:43 +0200 Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> 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! The other host, mutually declared as woring one, has net devices without IP addresses assigned added to the bridge - so the comparison lacks scruitiny, Thank you very much for fast responding ;-) Regards Oliver -- A FreeBSD user [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCaCoJpAAKCRCxzvs8Oqok r5dHAP4sHus4aLuLJcUk8DFuJpGmKGx8gn2d9CFo3pInn+X7iAEA60+GqufDx6UL Z9oNB+o1SC70v7sedd2np+jc2oz+iwU= =otEJ -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250518182404.3a760da9>