Date: Mon, 6 Feb 2017 23:14:40 +0100 From: Ruben <mail@osfux.nl> To: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: tap on lagg ? Message-ID: <1207dbb0-ec86-34fd-9a74-68d70b3b7892@osfux.nl> In-Reply-To: <66637AFA-D092-4EBB-B998-1BB2B2EE2CB4@up4.com> References: <11A193E5-555F-4733-B192-49A5FEDCFDEA@up4.com> <66637AFA-D092-4EBB-B998-1BB2B2EE2CB4@up4.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <vincent@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. What seems to be your predicament? Regards, Ruben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1207dbb0-ec86-34fd-9a74-68d70b3b7892>