Indeed, the wpa_supplicant log is much more interesting: wlp2s0: SME: Trying to authenticate with 20:9c:b4:d7:9a:f2 (SSID='eduroam' freq=5180 MHz) wlp2s0: Trying to associate with 20:9c:b4:d7:9a:f2 (SSID='eduroam' freq=5180 MHz) wlp2s0: Associated with 20:9c:b4:d7:9a:f2 wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 wlp2s0: CTRL-EVENT-EAP-STARTED EAP authentication started wlp2s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 wlp2s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected SSL: SSL3 alert: write (local SSL3 detected an error):fatal:protocol version OpenSSL: openssl_handshake - SSL_connect error:0A000102:SSL routines::unsupported protocol wlp2s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed wlp2s0: CTRL-EVENT-DISCONNECTED bssid=20:9c:b4:d7:9a:f2 reason=1 wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="eduroam" auth_failures=1 duration=10 reason=AUTH_FAILED BSSID 20:9c:b4:d7:9a:f2 ignore list count incremented to 2, ignoring for 10 seconds
This is apparently due to the network requiring authentication using a legacy SSL protocol: https://github.com/openssl/openssl/discussions/22642. This has caused issues in distributions where openssl was updated before: https://bbs.archlinux.org/viewtopic.php?id=286417. I will try to see if the answers proposed in this last link solve the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084553 Title: system cannot to connect to wpa2-enterprice PEAP mschapv2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2084553/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
