Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Jun 2022 14:25:16 +0000
From:      bugzilla-noreply@freebsd.org
To:        wireless@FreeBSD.org
Subject:   [Bug 264238] wpa_supplicant 2.10 fails to associate to open secondary VAP when primary VAP is WPA
Message-ID:  <bug-264238-21060-gj8S9C35es@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-264238-21060@https.bugs.freebsd.org/bugzilla/>
References:  <bug-264238-21060@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=3D264238

--- Comment #163 from Cy Schubert <cy@FreeBSD.org> ---
(In reply to Jaskie from comment #162)

There are two parts to this. wpa_supplicant exists in the base FreeBSD and =
it
exists in ports.

For base, I will add the PR to the commit log message. You will see the com=
mit
to main here, plus you will see the MFC (merge from current) commits here t=
oo.
Release Engineer said they will publish an EN. When they do you can
freebsd-update.

For ports, there are three separate ports: wpa_supplicant,
wpa_supplicant-devel, and wpa_supplicant29. The patch will be applied to
wpa_supplicant and wpa_supplicant-devel when I apply the patch to freebsd/m=
ain.
The patch will be merged to quarterly or more likely 2022Q3 will be cut by =
the
ports management team on July 1 negating my need to merge from ports main to
2022Q2.

We need to wait for the code review to complete. Also remember, this patch =
is a
temporary hack. It works by circumventing the whole issue but it does not
address the cause.

The fact that I am able to reproduce this problem on the same secondary VAP
using FreeBSD 14 and Fedora 36 but you are not able to do so with Debian
suggests either that Debian has addressed the flaw or there may be a driver
issue at play. Or, something else. With this in mind, I am considering buil=
ding
wpa_supplicant with -O0 to rule out llvm.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264238-21060-gj8S9C35es>