Date: Mon, 6 Feb 2017 21:15:58 -0500 From: Vincent Olivier <vincent@up4.com> To: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: tap on lagg ? Message-ID: <41619106-86D6-40EF-B84E-DC98A1B54FCD@up4.com> In-Reply-To: <1207dbb0-ec86-34fd-9a74-68d70b3b7892@osfux.nl> References: <11A193E5-555F-4733-B192-49A5FEDCFDEA@up4.com> <66637AFA-D092-4EBB-B998-1BB2B2EE2CB4@up4.com> <1207dbb0-ec86-34fd-9a74-68d70b3b7892@osfux.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Ruben, Thanks for this. > Le 6 févr. 2017 à 17:14, Ruben <mail@osfux.nl> a écrit : > > Hi 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). Didn’t try it it with disabling the tso/lro/vlanhwtagging features. Will try again with those disabled. > I have no experience in comparable setups without the vlan "layer" though. My setup didn’t involve vlans, only this: tap <—> bridge <—> lagg <—> igb0, igb1, igb2, igb3 Do you think that could be it? I have no need for a vlan here, though… > What seems to be your predicament? The tap would fail to « up » with an error message (that I forgot to note). I will try to do it again with the aforementioned features disabled (but without a vlan layer) and report back here. Vincent
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41619106-86D6-40EF-B84E-DC98A1B54FCD>