On Mon, Feb 6, 2017 at 4:14 PM, Ruben <m...@osfux.nl> wrote: > Hi Vincent, > > > >> BTW, I found this a couple of weeks ago and it has just been updated: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157182 >> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157182> >> >> >>> Le 6 févr. 2017 à 11:11, Vincent Olivier <vinc...@up4.com> a écrit : >>> >>> Hi, >>> >>> Has anyone succeeded in having a bhyve VM tap interface on an aggregate >>> interface (lagg)? From what I have read until now, it seems to be a known >>> problem, and my experience shows that it is still an issue with FreeBSD 11, >>> so I would like to know if it is because tap/bridging a lagg is not a >>> reasonable thing to do anyway… >>> >>> Regards, >>> >>> Vincent > > I have multiple machines on which 2 or more nics make up a LACP lagg > with vlans on it. Those vlan interfaces are in bridges together with the > tap interfaces that are in use by bhyve vms. > > Works as long as I "up" the nics in a specific fasion ( " -tso4 -lro > -vlanhwtag " ) . This works on 10.3 and 11.0 as far as I'm aware and I > have never experienced problems with it (Intel / AMD / em driver / bce > driver, re driver , all kinds of combinations). > > I have no experience in comparable setups without the vlan "layer" though.
I've gotten it to work both with and without vlan just by using -vlanhwtag. Leaving lro & tso4 enabled works fine. In fact, everything works fine with vlanhwtag enabled until I throw epair into the mix. This is using cxgbe/cxl. -Dustin _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
