Date: Mon, 17 Jan 2022 09:53:54 +0100 From: Kristof Provost <kp@FreeBSD.org> To: George Michaelson <ggm@algebras.org> Cc: "Patrick M. Hausen" <hausen@punkt.de>, freebsd-net@freebsd.org Subject: Re: can't bridge an I/F with jumbo to taps, deleted bridge 'flags' are sticky if you remake them Message-ID: <CC6C59E9-5E6D-4319-B19B-3010093A8646@FreeBSD.org> In-Reply-To: <CAKr6gn01GHV6DtQyOZbCca2e1f0T=pZyEM5%2B1775mBZuou6xKQ@mail.gmail.com> References: <CAKr6gn2QZ6AMEnVZyHs%2BbkCBxjcv0Q1sx-4HBsSh%2BQbCF6R9UA@mail.gmail.com> <FFF54034-A114-4DA7-BA1F-EDDA1DBC614D@punkt.de> <CAKr6gn01GHV6DtQyOZbCca2e1f0T=pZyEM5%2B1775mBZuou6xKQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 Jan 2022, at 6:09, George Michaelson wrote: > I tested on FreeBSD 13 and the behaviour is the same. > > But, I want to withdraw an imputation this is a bug. The underlying > behaviour is that you can't bond an MTU9000 and an MTU1500 interface. > If the base device is set jumbo, then the tapX instances must be set > jumbo. once you set MTU to match, it works fine on both FreeBSD12 and > on FreeBSD13. > > It's probably a documentation nit, if anything: bridged devices should > have identical MTU. The ifconfig bridge command will refuse to addm > <device> if the MTU is not correct for the any other member of the > bridge group. > Note that the if_bridge behaviour around MTU changes will change in 14. In 14 it becomes possible to change the MTU on the bridge itself, which w= ill then adjust the MTU for all member interfaces: https://cgit.freebsd.org/src/commit/sys/net/if_bridge.c?id=3D33306493825b= 291a308c0d37396e82de458f6cfe (And also https://cgit.freebsd.org/src/commit/sys/net/if.c?id=3D01ad0c007= 9646a31afa20e1f07e5b62b82613493 which means that interfaces belonging to = a bridge no longer allow MTU changes.) Br, Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CC6C59E9-5E6D-4319-B19B-3010093A8646>