Bug 217374 - fix tap(4) to be full-duplex and have non-zero speed
Summary: fix tap(4) to be full-duplex and have non-zero speed
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 11.0-STABLE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-net mailing list
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2017-02-26 15:01 UTC by snar
Modified: 2017-08-12 01:12 UTC (History)
2 users (show)

See Also:


Attachments
patch for if_tap.c (480 bytes, patch)
2017-02-26 15:01 UTC, snar
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description snar 2017-02-26 15:01:26 UTC
Created attachment 180317 [details]
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?revision=313038&view=markup#l478
[2]: https://svnweb.freebsd.org/base/stable/11/sys/net/ieee8023ad_lacp.c?revision=313038&view=markup#l952