Date: Sun, 26 Feb 2017 15:01:26 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 217374] tap(4) shall be full-duplex and have non-zero speed. Message-ID: <bug-217374-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217374 Bug ID: 217374 Summary: tap(4) shall be full-duplex and have non-zero speed. Product: Base System Version: 11.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: snar@snar.spb.ru Created attachment 180317 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180317&action= =3Dedit patch for if_tap.c For now tap(4) devices advertise itself as just 'ethernet autoselect', without duplex or speed capabilities. This advertisement makes them unable to be aggregated into lacp-based lagg(4): - lacp code requires underlying interfaces to be full-duplex, else interface will not participate in lacp at all[1] - lacp code requires underlying interface to have non-zero speed, else this interface can not be selected as active aggregator[2]. [1]: https://svnweb.freebsd.org/base/stable/11/sys/net/ieee8023ad_lacp.c?revisio= n=3D313038&view=3Dmarkup#l478 [2]: https://svnweb.freebsd.org/base/stable/11/sys/net/ieee8023ad_lacp.c?revisio= n=3D313038&view=3Dmarkup#l952 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217374-8>