From nobody Sun May 18 17:48:47 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 4b0pGY068hz5wYf7 for ; Sun, 18 May 2025 17:49:09 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 ECDSA (prime256v1) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4b0pGX2qcqz3mX5 for ; Sun, 18 May 2025 17:49:08 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none 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 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1747590546; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=F1N5dBxeNEwotQ5YRma5PL4kpbK3T2n/qsLePD9BP/M=; b=0uTjvZjc8Ug4tbOL6JVSO5RfGjmpYa+1WhCtXcEIOWXU1NrXwzoM78PqXYAvtr/lVnnQ0T Oku8pDWJEyeQnLhZWLMNXdpBerz4attzJWIUAXd4K0WxIO/BLRijdLFVPlnsbCdlYBGHeE SzpOYxhD67AIpMHarwlU0HiqJ2xeg+wXlt6uV6my5Vpl9fJufgpmEA/n6WKyi1gdAELI2S gSdp2TRaI1KTfZVDzS9NEpSaW1a2TGac1iVa76AXgaiiBif4cBHXbOYY+fTN2DXfgmvEvF B8MIlG96XI97r/v/OzN45ekj7Rv3mP2gPqaGtJk7Pcsd8Q1BbtwHR6UiJD8DRA== Date: Sun, 18 May 2025 19:48:47 +0200 From: Alexander Leidinger To: A FreeBSD User Cc: Marek Zarychta , FreeBSD CURRENT Subject: Re: CURRENT: can not add device to bridge: ifconfig: BRDGADD igb0: Invalid argument 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> Message-ID: <1ca30cdfb783848eafce24b77f10c0a5@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_ee28aabe9259dc63dae65dda37c1ace8"; micalg=pgp-sha256 X-Rspamd-Queue-Id: 4b0pGX2qcqz3mX5 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:34240, ipnet:89.238.64.0/18, country:DE] X-Spamd-Bar: ---- This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_ee28aabe9259dc63dae65dda37c1ace8 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed 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. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_ee28aabe9259dc63dae65dda37c1ace8 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----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----- --=_ee28aabe9259dc63dae65dda37c1ace8--