Date: Fri, 24 Mar 2023 04:58:40 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 224961] VLAN ID 0 Not Supported Message-ID: <bug-224961-7501-8dE3ZXaQ1p@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 topsecretsauce <xerowingsx9k@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerowingsx9k@gmail.com --- Comment #14 from topsecretsauce <xerowingsx9k@gmail.com> --- I am also experiencing this issue. I think another way of describing what we may be seeing is that WPA_Supplic= ant may be unable to process requests tagged with VID 0. This may be similar to= how dhclient was unable to do so until Franco worked on having dhclient decapsu= late VID 0. I am using a netgraph configuration on 13.1 that filters out 802.1Q information if it contains VID 0 and from looking at the CAP for that netgr= aph interface, it appears to respond to EAP Identity requests normally. And like the others, if I simply use WPA_Supplicant with the physical interface and = let it receive the VID 0 EAP identity request traffic, it doesn't respond to the identity requests. What we may need is for WPA_Supplicant to decapsulate 802.1Q information fr= om the frame if there's a VID of 0. --=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-8dE3ZXaQ1p>