Date: Tue, 27 Feb 2024 20:28:49 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 277356] iwlwifi(4): unable to associate to AP if set `ether random` Message-ID: <bug-277356-21060-uxJQMU3Sv1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277356-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-277356-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=3D277356 Bjoern A. Zeeb <bz@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bz@FreeBSD.org Status|New |Open --- Comment #2 from Bjoern A. Zeeb <bz@FreeBSD.org> --- (In reply to Li-Wen Hsu from comment #0) I didn't even know we had that feature in ifconfig. Given the order you are running this I wouldn't know why it shouldn't work. Do you get any logging from iwlwifi? Given you do start wpa_supplicant with lots of debugging, what does it thin= k?=20 Any specific errors there? Alternatively before you do the ifconfig wlan0 up/start wpa_supplicant, can= you in a 2nd terminal start ifconfig -v wlan0 > /var/tmp/iwlwifi.txt tcpdump -ln -s0 -e -vvv -i wlan0 -y IEEE802_11_RADIO -w /var/tmp/iwlwifi.pc= ap and send bz/cc the two files so we can have a peak. Or maybe you already = see something yourself if you open it in wireshark. --=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-277356-21060-uxJQMU3Sv1>