Date: Fri, 14 Jun 2024 20:17:09 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 277356] iwlwifi(4): unable to associate to AP if set `ether random` (LinuxKPI 802.11 compat code problem?) Message-ID: <bug-277356-21060-Zt8zmUaNUE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277356-21060@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277356 Bjoern A. Zeeb <bz@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|wireless@FreeBSD.org |bz@FreeBSD.org Status|Open |In Progress Summary|iwlwifi(4): unable to |iwlwifi(4): unable to |associate to AP if set |associate to AP if set |`ether random` |`ether random` (LinuxKPI | |802.11 compat code | |problem?) --- Comment #4 from Bjoern A. Zeeb <bz@FreeBSD.org> --- And as a note to myself: We do memcpy(vif->addr, mac, IEEE80211_ADDR_LEN); in vap_create() but we likely do not synch it again afterwards. So that could be the problem. We likely should re-synch all that state (or what is needed) when coming out of INIT before going into SCAN (as scan also may depend on that addr). We should also go and see if we can implement the equivalent of NL80211_SCAN_FLAG_RANDOM_ADDR which most LinuxKPI based drivers would honor. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277356-21060-Zt8zmUaNUE>