[Bug 258527] wpa_supplicant(8) from the base brings up wlan(4) interface incorrectly
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258527] wpa_supplicant(8) from the base brings up wlan(4) interface incorrectly"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface incorrectly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 16 Sep 2021 07:10:40 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 Bug ID: 258527 Summary: wpa_supplicant(8) from the base brings up wlan(4) interface incorrectly Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: zarychtam@plan-b.pwste.edu.pl Created attachment 227932 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=227932&action=edit log file After updating stable/13 to the most recent version I am no more able to connect to EAP/PEAP secured WiFi network. Authentication goes fine but at the end wpa_supplicant dumps core leaving wlan0 with "no carrier" status. Connecting to WPA/WPA2 secured WiFi network with the same wpa_supplicant is still possible. To workaround this one has to install security/wpa_supplicant from ports which works flawlessly. -- You are receiving this mail because: You are the assignee for the bug.