Date: Sat, 25 Jun 2022 07:44:13 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 264883] ena and epair interfaces cannot be members of the same bridge Message-ID: <bug-264883-227-0fLmTQPOoX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264883-227@https.bugs.freebsd.org/bugzilla/> References: <bug-264883-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264883 Kristof Provost <kp@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kp@freebsd.org --- Comment #1 from Kristof Provost <kp@freebsd.org> --- I suspect the problem here is one of MTU. if_bridge sets its MTU to that of the first interface added to it. That's either 9001 (ena) or 1500 (epair). When you try to add the second interface= it the MTU does not match and the interface is not added. There should be a log in `dmesg` saying 'bridge0: invalid MTU: 9001(ena0) != =3D 1500' or something like it. You should be able to fix that by changing the ena or epair MTU prior to ad= ding it to the bridge. You should also know that the behaviour of if_bridge has been changed in 14, where it will change the MTU of newly added members, rather than rejecting them. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264883-227-0fLmTQPOoX>