Networkmanager

wpa_supplicant 不再連接到 eduroam

  • December 14, 2018

幾週後(可能是在 dist 升級之後)我的機器無法再連接到 802.1x 網路。我將 Debian Buster 與 i3 一起使用,但使用的是 nm-applet。我也嘗試過直接與 wpa_supplicant 連接,但它也不起作用。這是我的配置:

[connection]
id=eduroam
uuid=a86d2f21-990c-4a55-b7e4-933ffcffe0cd
type=wifi
permissions=user:root:;

[wifi]
mac-address-blacklist=
ssid=eduroam

[wifi-security]
group=ccmp;tkip;
key-mgmt=wpa-eap
pairwise=ccmp;
proto=rsn;

[802-1x]
altsubject-matches=DNS:nps1.unitn.it;DNS:nps2.unitn.it;DNS:nps3.unitn.it;
anonymous-identity=
ca-cert=/root/.cat_installer/ca.pem
eap=peap;
identity=[removed]
password=[secret]
phase2-auth=mschapv2

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto

這是系統日誌的輸出:

wpa_supplicant[1075]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="eduroam"
wpa_supplicant[1075]: wlan0: SME: Trying to authenticate with 00:26:0b:ac:91:d2 (SSID='eduroam' freq=2412 MHz)
wpa_supplicant[1075]: wlan0: Trying to associate with 00:26:0b:ac:91:d2 (SSID='eduroam' freq=2412 MHz)
wpa_supplicant[1075]: wlan0: Associated with 00:26:0b:ac:91:d2
wpa_supplicant[1075]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wpa_supplicant[1075]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=IT
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 -> NAK
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
wpa_supplicant[1075]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:26:0b:ac:91:d2 reason=4 locally_generated=1
wpa_supplicant[1075]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wpa_supplicant[1075]: wlan0: SME: Trying to authenticate with 54:75:d0:3f:4d:2d (SSID='eduroam' freq=5200 MHz)
wpa_supplicant[1075]: wlan0: Trying to associate with 54:75:d0:3f:4d:2d (SSID='eduroam' freq=5200 MHz)
wpa_supplicant[1075]: wlan0: Associated with 54:75:d0:3f:4d:2d
wpa_supplicant[1075]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wpa_supplicant[1075]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=IT
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 -> NAK
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=eduradius-dr-2018' hash=86fdb85978a8d3c9ba28e40f1f10415d49c0a595b8752556906d37ac9d1884fc
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=eduradius-dr-2018' hash=86fdb85978a8d3c9ba28e40f1f10415d49c0a595b8752556906d37ac9d1884fc
wpa_supplicant[1075]: wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wpa_supplicant[1075]: wlan0: Authentication with 54:75:d0:3f:4d:2d timed out.
wpa_supplicant[1075]: wlan0: CTRL-EVENT-DISCONNECTED bssid=54:75:d0:3f:4d:2d reason=3 locally_generated=1
wpa_supplicant[1075]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="eduroam" auth_failures=2 duration=23 reason=AUTH_FAILED
wpa_supplicant[1075]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

除了等待更新我還能做什麼?

更新,dmseg -wL 輸出:

[72642.755504] wlan0: authenticate with 54:75:d0:3f:4d:22
[72642.757856] wlan0: send auth to 54:75:d0:3f:4d:22 (try 1/3)
[72642.761033] wlan0: authenticated
[72642.763678] wlan0: associate with 54:75:d0:3f:4d:22 (try 1/3)
[72642.766431] wlan0: RX AssocResp from 54:75:d0:3f:4d:22 (capab=0x431 status=0 aid=3)
[72642.768628] wlan0: associated
[72642.863828] wlan0: Limiting TX power to 17 dBm as advertised by 54:75:d0:3f:4d:22
[72647.757757] wlan0: deauthenticated from 54:75:d0:3f:4d:22 (Reason: 3=DEAUTH_LEAVING)

更新:似乎問題是 wpa_supplicant 2.6 我通過降級到 2.4 解決了這個問題

我通過將 wpasupplicant 從 2.6 版降級到 2.4 版解決了這個錯誤

我記得在我的大學裡也遇到過類似的問題。事實證明,接入點收到的韌體更新破壞了對某些 WIFI 適配器的支持。

由於連接失敗的原因是“AUTH_FAILED”而不是“WRONG_KEY”之類的東西,我會詢問您的 eduroam 網路的管理員是否知道某些不兼容性。

同時,您可以檢查核心日誌是否包含有關 WIFI 適配器韌體問題的一些資訊。打開終端並觀察dmesg -wL嘗試連接網路時的輸出。如果您發現有問題,請在此處發布,也許我們可以找出問題所在。

引用自:https://unix.stackexchange.com/questions/482727