Date: Tue, 20 Sep 2016 16:24:13 -0400 From: Robert Blayzor <rblayzor.bulk@inoc.net> To: dweimer@dweimer.net Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: LAGG and Jumbo Frames Message-ID: <8C764584-DCA9-4407-84E8-AFDC52B35AE1@inoc.net> In-Reply-To: <48926c6013f938af832c17e4ad10b232@dweimer.net> References: <48926c6013f938af832c17e4ad10b232@dweimer.net>
next in thread | previous in thread | raw e-mail | index | archive | help
If your lag interface is up, what=E2=80=99s not working? Does something like this work? ping -D -s 8972 <ip L2 adjacent host> and then this not? ping -D -s 8972 <gateway> If your firewall is on the LAN side supporting jumbo frames ok, but not = WAN side, then the router will have to fragment all of the packets. = (unless DF bit is set of course).=20 -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu > On Sep 19, 2016, at 3:23 PM, Dean E. Weimer <dweimer@dweimer.net> = wrote: >=20 > Does anyone see an issue with the Jumbo Frames setup above, or are = Jumbo Frames not supported correctly in a LACP Aggregate configuration.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8C764584-DCA9-4407-84E8-AFDC52B35AE1>