[Bug 217374] fix tap(4) to be full-duplex and have non-zero speed
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 31 May 2023 15:54:40 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217374
--- Comment #1 from commit-hook@FreeBSD.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=0ec220df526d38c73650301c1300a6fe3124698a
commit 0ec220df526d38c73650301c1300a6fe3124698a
Author: Alexandre Snarskii <snar@snar.spb.ru>
AuthorDate: 2023-05-31 15:50:00 +0000
Commit: Warner Losh <imp@FreeBSD.org>
CommitDate: 2023-05-31 15:53:48 +0000
tap(4): allow full-duplex and non-zero speed
tap(4) devices advertise themselves 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
- lacp code requires underlying interface to have non-zero speed, else
this interface can not be selected as active aggregator
PR: 217374
Reported-by: Alexandre Snarskii <snar@snar.spb.ru>
Co-authored-by: Mina Galić <freebsd@igalic.co>
Reviewed-by: imp,karles
Pull-request: https://github.com/freebsd/freebsd-src/pull/745
sys/net/if_tuntap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
You are receiving this mail because:
You are the assignee for the bug.