May not be specific to 11.0-RC3, but since that's what I was running
when trying to set this up I am posting to stable mailing list first.
I was trying to setup an LACP 3 port aggregate connection and having all
kinds of problems, At first I thought it was an issue with NAT
reflection and my firewall because I could ping the IPs and ssh to the
system but I couldn't connect to the services. oddly enough I could
connect from devices outside of my network and once I realized that I
could also connect from wireless devices I realized the common thread
was that the Internet pipe and Access points didn't support Jumbo
Frames. disabling Jumbo frames on the interfaces restored connectivity
to the LACP aggregate connection. I guess this could be an issue with
the switch as well I don't have any other LACP enabled devices to test
this with.
my configuration:
rc.conf settings (working):
hostname="freebsd.dweimer.local"
ifconfig_igb0="up"
ifconfig_igb1="up"
ifconfig_igb2="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport igb0 laggport igb1 laggport igb2
10.9.5.5/24"
rc.conf settings (Jumbo frames Broken):
hostname="freebsd.dweimer.local"
ifconfig_igb0="up mtu 9000"
ifconfig_igb1="up mtu 9000"
ifconfig_igb2="up mtu 9000"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport igb0 laggport igb1 laggport igb2
10.9.5.5/24"
Does anyone see an issue with the Jumbo Frames setup above, or are Jumbo
Frames not supported correctly in a LACP Aggregate configuration.
--
Thanks,
Dean E. Weimer
http://www.dweimer.net/
This is almost certainly a PMTUd issue. Unless your end-to-end paths to everything you talk to have jumboframes configured, there's no benefit to setting them up on the lagg. Just go with the default MTU. --lyndon
If your lag interface is up, what?s 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). -- 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 at dweimer.net> wrote: > > Does anyone see an issue with the Jumbo Frames setup above, or are Jumbo Frames not supported correctly in a LACP Aggregate configuration.