Date: Sun, 18 May 2025 19:48:47 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: A FreeBSD User <freebsd@walstatt-de.de> Cc: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument Message-ID: <1ca30cdfb783848eafce24b77f10c0a5@Leidinger.net> In-Reply-To: <20250518182404.3a760da9@thor.sb211.local> References: <20250518180658.2e58d55a@thor.sb211.local> <192c8e37-4a85-4916-9986-0a556333a527@plan-b.pwste.edu.pl> <20250518182404.3a760da9@thor.sb211.local>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Am 2025-05-18 18:23, schrieb A FreeBSD User: > 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! You want to make it work without this. Short: use the IP on the bridge itself, not in the member IF. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmgqHY4ACgkQEg2wmwP4 2IY1qRAAkLU6QCgSIGPdd5dKLRe1XaUURaFLnFM1NRqxOsqMXIzjHDj2m/+AHHHv 0KzERIdjycyIoj2bGB8uEJn0N4bE7tkrdtc/czP8YX16P4cbl/bEjO21baQ+/9c+ kVtCwpVwYIlvwww1iHKwoduhusTlVuu0HTIzJqeja9fSA82TfHn1xduqZ7Yr4NV+ 8RykSTSMwSPyxMe8kCdxD9Q0x6+jidQ+MPrRQNtmZ+/uxIKFd4PfF7EUKgrs5LkW gO6GCLSF1AIGW8fK1TRXnFZUnc5aqSAQuMsknBHXFKuNpSRINV4EQE/YAgfE3/mN +6XHUXQLoeiSZwC/XDF8+SlVeFmsPJfm11tGNEqJla+jO2ByZilymFQdXc/SAeDd tirDD2mXqn1430kNAzRcb0IVhaqMmrHpDr1O4E/X6hOaQsD76lRH4QXy2PHegKPO TVmPGPiey9Df9Pk6oxCopQQtvqPovYak/M8cI1H1DufLypZ7fUQhV7bJRwPbhtq5 7XLehM0+rC72GWxjXyyrLRY4nwfzyBfRt0mME67L2oVnZn2adkZwCCIO455uG+Cc i4AZ7rvFenefBnzvLEbhPDrES0g5fRUlpD5rXLUJ1EBdmJzHNbIMBi4XWRc78pRd QRFgdu8iN1asZAr896B6vu6X6eGHkvCh0Ir2EBmhUZ5qGQk9LXI= =sT5A -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1ca30cdfb783848eafce24b77f10c0a5>