Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Sep 2022 06:20:01 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 224961] VLAN ID 0 Not Supported
Message-ID:  <bug-224961-7501-Z2Zi7CKSJT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224961-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-224961-7501@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224961

--- Comment #10 from crb <crb@ChrisBowman.com> ---
Hans,
I greatly appreciate your previous feedback here!  Thank you

This does indeed seem to work to issue vlan 0 packets, at least as far as I=
 can
understand looking at tcpdump output on a stock 13.1 system.  However, I th=
ink
it's tagging all traffic as vlan 0.  I think it shouldn't be tagging BPDU
(Bridge Protocol Data Unit) traffic that way.  My wpa_supplicant packets
(EAPoL) look like they're also being taged as vlan 0 and I think that's why
authentication isn't happening for me.  Should EAPoL packets be tagged with=
 a
vlan?
Christopher

--=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-224961-7501-Z2Zi7CKSJT>