[SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

Sveske-juice · 2022-09-08 10:46:10

I have a problem where I can't connect to my schools wifi network which uses wpa 2 enterprise protocol. It used to work flawlessly after creating a network connection manually following this: https://askubuntu.com/questions/262491/ … 835_839763

My friend which also uses archlinux, tried the do the same in the ubuntu link however it did not work for him. Therefore i let him try connect with his credentials on my computer, which didn't work either.
After that i tried connecting again with my own credentials but now I can't even connect myself. I can not use the guest network because i need to access the school's printers as well as other things.

When i try to connect i get the following in my system log:

$ sudo dmesg -w
[  610.320715] audit: type=1111 audit(1662633482.508:95): pid=932 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=9668172d-70de-488b-af70-d8bef881e40b name="Next" pid=1953 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  610.399281] wlan0: authenticate with 00:d7:8f:34:b1:ed
[  610.399300] wlan0: Invalid HE elem, Disable HE
[  610.402766] wlan0: send auth to 00:d7:8f:34:b1:ed (try 1/3)
[  610.432254] wlan0: authenticated
[  610.432730] wlan0: associate with 00:d7:8f:34:b1:ed (try 1/3)
[  610.434552] wlan0: RX AssocResp from 00:d7:8f:34:b1:ed (capab=0x11 status=0 aid=5)
[  610.439744] wlan0: associated
[  610.486552] wlan0: Limiting TX power to 21 (21 - 0) dBm as advertised by 00:d7:8f:34:b1:ed
[  610.546451] wlan0: deauthenticated from 00:d7:8f:34:b1:ed (Reason: 23=IEEE8021X_FAILED)
[  620.978075] wlan0: authenticate with 00:d7:8f:34:b1:ed
[  620.978098] wlan0: Invalid HE elem, Disable HE
[  620.982188] wlan0: send auth to 00:d7:8f:34:b1:ed (try 1/3)
[  621.112836] wlan0: send auth to 00:d7:8f:34:b1:ed (try 2/3)
[  621.216413] wlan0: send auth to 00:d7:8f:34:b1:ed (try 3/3)
[  621.319721] wlan0: authentication with 00:d7:8f:34:b1:ed timed out
[  622.739831] wlan0: authenticate with 00:d7:8f:b8:37:0d
[  622.739852] wlan0: Invalid HE elem, Disable HE
[  622.743090] wlan0: send auth to 00:d7:8f:b8:37:0d (try 1/3)
[  622.777176] wlan0: authenticated
[  622.781417] wlan0: associate with 00:d7:8f:b8:37:0d (try 1/3)
[  622.783677] wlan0: RX AssocResp from 00:d7:8f:b8:37:0d (capab=0x11 status=0 aid=1)
[  622.788746] wlan0: associated
[  622.831132] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 00:d7:8f:b8:37:0d
[  630.995798] wlan0: deauthenticated from 00:d7:8f:b8:37:0d (Reason: 2=PREV_AUTH_NOT_VALID)
[  631.336431] wlan0: authenticate with 00:d7:8f:52:82:c2
[  631.336451] wlan0: bad VHT capabilities, disabling VHT
[  631.336453] wlan0: Invalid HE elem, Disable HE
[  631.336454] wlan0: 80 MHz not supported, disabling VHT
[  631.338485] wlan0: send auth to 00:d7:8f:52:82:c2 (try 1/3)
[  631.407292] wlan0: authenticated
[  631.409901] wlan0: associate with 00:d7:8f:52:82:c2 (try 1/3)
[  631.417006] wlan0: RX AssocResp from 00:d7:8f:52:82:c2 (capab=0x11 status=0 aid=1)
[  631.443328] wlan0: associated
[  631.495327] wlan0: Limiting TX power to 18 (18 - 0) dBm as advertised by 00:d7:8f:52:82:c2
[  635.885632] wlan0: deauthenticating from 00:d7:8f:52:82:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
[  636.033165] audit: type=1334 audit(1662633508.221:96): prog-id=21 op=LOAD
[  636.033227] audit: type=1334 audit(1662633508.221:97): prog-id=22 op=LOAD
[  636.033263] audit: type=1334 audit(1662633508.221:98): prog-id=23 op=LOAD
[  636.067539] audit: type=1130 audit(1662633508.254:99): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  639.512104] wlan0: authenticate with 00:d7:8f:b8:37:0d
[  639.512120] wlan0: Invalid HE elem, Disable HE
[  639.516058] wlan0: send auth to 00:d7:8f:b8:37:0d (try 1/3)
[  639.545775] wlan0: authenticated
[  639.546293] wlan0: associate with 00:d7:8f:b8:37:0d (try 1/3)
[  639.565614] wlan0: RX AssocResp from 00:d7:8f:b8:37:0d (capab=0x11 status=0 aid=2)
[  639.571226] wlan0: associated
[  639.625152] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 00:d7:8f:b8:37:0d
[  647.997635] wlan0: deauthenticated from 00:d7:8f:b8:37:0d (Reason: 2=PREV_AUTH_NOT_VALID)
[  659.891160] wlan0: authenticate with 00:d7:8f:b8:37:0d
[  659.891182] wlan0: Invalid HE elem, Disable HE
[  659.894666] wlan0: send auth to 00:d7:8f:b8:37:0d (try 1/3)
[  659.924230] wlan0: authenticated
[  659.926460] wlan0: associate with 00:d7:8f:b8:37:0d (try 1/3)
[  659.928330] wlan0: RX AssocResp from 00:d7:8f:b8:37:0d (capab=0x11 status=0 aid=1)
[  659.933822] wlan0: associated
[  660.003415] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 00:d7:8f:b8:37:0d
[  663.884635] wlan0: deauthenticating from 00:d7:8f:b8:37:0d by local choice (Reason: 3=DEAUTH_LEAVING)

I've tried reinstalling NetworkManager as well as deleting the manually added network connection created from the ubuntu link and adding it again.

Sys info:
kernel version:

$ uname -r
5.19.7-arch1-1

networkmanager installed version:

$ pacman -Q | grep networkmanager
networkmanager 1.40.0-1

network card:

$ lspci | grep -i Wi-fi
03:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)

Last edited by Sveske-juice (2022-09-13 11:43:52)

V1del · 2022-09-08 11:42:12

What changed between now and when you were last able to connect? Likely culprits here are the kernel and/or linux-firmware, I'd try to downgrade linux-firmware one version to check this.

seth · 2022-09-08 14:02:19

There're two APs showing up, 00:d7:8f:34:b1:ed and 00:d7:8f:b8:37:0d
The former fails on IEEE8021X_FAILED the latter on PREV_AUTH_NOT_VALID what could be a protocol (encryption algorithm), bad credentials (your friend) or carrier (weak signal, driver crashes) issue.
Or something entirely different.

And then there's

[  659.891160] wlan0: authenticate with 00:d7:8f:b8:37:0d
[  659.891182] wlan0: Invalid HE elem, Disable HE
[  659.894666] wlan0: send auth to 00:d7:8f:b8:37:0d (try 1/3)
[  659.924230] wlan0: authenticated
[  659.926460] wlan0: associate with 00:d7:8f:b8:37:0d (try 1/3)
[  659.928330] wlan0: RX AssocResp from 00:d7:8f:b8:37:0d (capab=0x11 status=0 aid=1)
[  659.933822] wlan0: associated
[  660.003415] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 00:d7:8f:b8:37:0d
[  663.884635] wlan0: deauthenticating from 00:d7:8f:b8:37:0d by local choice (Reason: 3=DEAUTH_LEAVING)

where you successfully connect w/ the AP 00:d7:8f:b8:37:0d but after ~4 seconds quit.
What sounds eerily like conflicting services knocking each other out - or NM thinks the AP at 00:d7:8f:34:b1:ed looks more attractive and wants to go on connecting there.

=> post a complete system journal covering a connection attempt.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Sveske-juice · 2022-09-09 15:09:44

seth wrote:

=> post a complete system journal covering a connection attempt.

I am only able to retry this on monday, but i have a journal file from the day I tried. I uploaded it to: http://0x0.st/ofwV.txt

I disconnect from the guest network and try to connect to the network on line 1910.

On line 1971 it says:

device (wlan0): Activation: (wifi) connection 'Next' has security, and secrets exist.  No new secrets needed.

maybe I can try clearing the secrets, but how can i do that? i have tried removing the connection and adding it again and typing in my username and password.

Last edited by Sveske-juice (2022-09-09 15:15:54)

seth · 2022-09-09 16:09:13

You have one EAP failure on bssid=00:d7:8f:34:b1:ed

Sep 08 12:05:50 Sussyamug wpa_supplicant[1179]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
Sep 08 12:05:50 Sussyamug wpa_supplicant[1179]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 -> NAK
Sep 08 12:05:50 Sussyamug wpa_supplicant[1179]: wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed

Since there's only 25 tried and the other side doesn't like that you maybe need a different method? TLS or TTLS next to PEAP?
Do you have a journal from when it still worked?
What does your connection file look like (you can of course obfuscate the private stuff)?

(Afterwards you're trying to roam to 00:d7:8f:b8:37:0d what fails because PREV_AUTH_NOT_VALID your previous attempt failed and then there're two local aborts from 00:d7:8f:52:82:c2 and 00:d7:8f:b8:37:0d so this is probably just noise in resonse to the original failure.)

Sveske-juice · 2022-09-09 17:13:34

seth wrote:

What does your connection file look like (you can of course obfuscate the private stuff)?

Yes i have that. This should be what is relevant:

Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.4604] device (wlan0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.4961] dhcp4 (wlan0): canceled DHCP transaction
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.4962] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.4962] dhcp4 (wlan0): state changed no lease
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5283] device (wlan0): set-hw-addr: set MAC address to 32:E3:3F:25:45:7E (scanning)
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5391] manager: NetworkManager state is now DISCONNECTED
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5395] device (wlan0): Activation: starting connection 'Next' (6659d7e9-d62c-4890-b6f2-1a5a595e3c6e)
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5401] device (wlan0): supplicant interface state: completed -> disconnected
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5401] device (p2p-dev-wlan0): supplicant management interface state: completed -> disconnected
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5411] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5416] manager: NetworkManager state is now CONNECTING
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5879] device (wlan0): set-hw-addr: reset MAC address to C8:E2:65:0E:6A:82 (preserve)
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5896] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5899] device (wlan0): Activation: (wifi) access point 'Next' has security, but secrets are required.
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5900] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5907] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5908] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5923] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5927] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5932] device (wlan0): Activation: (wifi) connection 'Next' has security, and secrets exist.  No new secrets needed.
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5933] Config: added 'ssid' value 'Next'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5933] Config: added 'scan_ssid' value '1'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5934] Config: added 'bgscan' value 'simple:30:-65:300'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5934] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5934] Config: added 'auth_alg' value 'OPEN'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5934] Config: added 'password' value '<hidden>'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5934] Config: added 'eap' value 'FAST PEAP'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5935] Config: added 'fragment_size' value '1266'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5935] Config: added 'phase1' value 'fast_provisioning=1'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5935] Config: added 'pac_file' value 'blob://pac-blob-6659d7e9-d62c-4890-b6f2-1a5a595e3c6e'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5935] Config: added 'identity' value 'carl2792'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.5935] Config: added 'proactive_key_caching' value '1'
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.6310] device (wlan0): supplicant interface state: interface_disabled -> disconnected
Aug 29 12:10:42 Sussyamug NetworkManager[910]: <info>  [1661767842.6310] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> disconnected
Aug 29 12:10:42 Sussyamug wpa_supplicant[1148]: wlan0: Reject scan trigger since one is already pending
Aug 29 12:10:42 Sussyamug wpa_supplicant[1148]: wlan0: Failed to initiate AP scan
Aug 29 12:10:43 Sussyamug wpa_supplicant[1148]: wlan0: Reject scan trigger since one is already pending
Aug 29 12:10:43 Sussyamug wpa_supplicant[1148]: wlan0: Failed to initiate AP scan
Aug 29 12:10:44 Sussyamug NetworkManager[910]: <info>  [1661767844.6406] device (wlan0): supplicant interface state: disconnected -> scanning
Aug 29 12:10:44 Sussyamug NetworkManager[910]: <info>  [1661767844.6407] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: SME: Trying to authenticate with 00:d7:8f:e6:45:ed (SSID='Next' freq=5580 MHz)
Aug 29 12:10:45 Sussyamug kernel: wlan0: authenticate with 00:d7:8f:e6:45:ed
Aug 29 12:10:45 Sussyamug kernel: wlan0: Invalid HE elem, Disable HE
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.4591] device (wlan0): supplicant interface state: scanning -> authenticating
Aug 29 12:10:45 Sussyamug kernel: wlan0: send auth to 00:d7:8f:e6:45:ed (try 1/3)
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.4591] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: Trying to associate with 00:d7:8f:e6:45:ed (SSID='Next' freq=5580 MHz)
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.4911] device (wlan0): supplicant interface state: authenticating -> associating
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.4912] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Aug 29 12:10:45 Sussyamug kernel: wlan0: authenticated
Aug 29 12:10:45 Sussyamug kernel: wlan0: associate with 00:d7:8f:e6:45:ed (try 1/3)
Aug 29 12:10:45 Sussyamug kernel: wlan0: RX AssocResp from 00:d7:8f:e6:45:ed (capab=0x11 status=0 aid=10)
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: Associated with 00:d7:8f:e6:45:ed
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Aug 29 12:10:45 Sussyamug kernel: wlan0: associated
Aug 29 12:10:45 Sussyamug kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 00:d7:8f:e6:45:ed
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.5072] device (wlan0): supplicant interface state: associating -> associated
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.5072] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=Nextdc1.next.local' hash=9fe4ebf859d4ddc17e0f91874a38268dd214f024587c2c9fda7fbf269d5b7c>
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:Nextdc1.next.local
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=Nextdc1.next.local' hash=9fe4ebf859d4ddc17e0f91874a38268dd214f024587c2c9fda7fbf269d5b7c>
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=Nextdc1.next.local' hash=9fe4ebf859d4ddc17e0f91874a38268dd214f024587c2c9fda7fbf269d5b7c>
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:Nextdc1.next.local
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=Nextdc1.next.local' hash=9fe4ebf859d4ddc17e0f91874a38268dd214f024587c2c9fda7fbf269d5b7c>
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:Nextdc1.next.local
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=Nextdc1.next.local' hash=9fe4ebf859d4ddc17e0f91874a38268dd214f024587c2c9fda7fbf269d5b7c>
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:Nextdc1.next.local
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: EAP-MSCHAPV2: Authentication succeeded
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: PMKSA-CACHE-ADDED 00:d7:8f:e6:45:ed 0
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: WPA: Key negotiation completed with 00:d7:8f:e6:45:ed [PTK=CCMP GTK=CCMP]
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:d7:8f:e6:45:ed completed [id=0 id_str=]
Aug 29 12:10:45 Sussyamug kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Aug 29 12:10:45 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=9999 txrate=26000
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.7373] device (wlan0): supplicant interface state: associated -> completed
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.7374] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Next"
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.7374] device (p2p-dev-wlan0): supplicant management interface state: associated -> completed
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.7376] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 29 12:10:45 Sussyamug NetworkManager[910]: <info>  [1661767845.7381] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Aug 29 12:10:47 Sussyamug NetworkManager[910]: <info>  [1661767847.8666] dhcp4 (wlan0): state changed new lease, address=10.78.66.121
Aug 29 12:10:47 Sussyamug NetworkManager[910]: <info>  [1661767847.8674] policy: set 'Next' (wlan0) as default for IPv4 routing and DNS
Aug 29 12:10:47 Sussyamug NetworkManager[910]: <info>  [1661767847.8789] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug 29 12:10:47 Sussyamug NetworkManager[910]: <info>  [1661767847.8814] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug 29 12:10:47 Sussyamug NetworkManager[910]: <info>  [1661767847.8817] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug 29 12:10:47 Sussyamug NetworkManager[910]: <info>  [1661767847.8822] manager: NetworkManager state is now CONNECTED_SITE
Aug 29 12:10:47 Sussyamug NetworkManager[910]: <info>  [1661767847.8834] device (wlan0): Activation: successful, device activated.
Aug 29 12:10:47 Sussyamug NetworkManager[910]: <info>  [1661767847.8844] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 29 12:10:52 Sussyamug systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Aug 29 12:10:52 Sussyamug audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? add>
Aug 29 12:10:52 Sussyamug kernel: audit: type=1131 audit(1661767852.384:156): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/sy>
Aug 29 12:11:19 Sussyamug rtkit-daemon[1693]: Supervising 7 threads of 4 processes of 1 users.
Aug 29 12:11:19 Sussyamug rtkit-daemon[1693]: Supervising 7 threads of 4 processes of 1 users.
Aug 29 12:11:19 Sussyamug rtkit-daemon[1693]: Supervising 7 threads of 4 processes of 1 users.
Aug 29 12:11:19 Sussyamug rtkit-daemon[1693]: Supervising 7 threads of 4 processes of 1 users.
Aug 29 12:11:34 Sussyamug rtkit-daemon[1693]: Supervising 7 threads of 4 processes of 1 users.
Aug 29 12:11:34 Sussyamug rtkit-daemon[1693]: Supervising 7 threads of 4 processes of 1 users.
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.2954] device (wlan0): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed')
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.2958] manager: NetworkManager state is now DISCONNECTING
Aug 29 12:11:58 Sussyamug audit[910]: USYS_CONFIG pid=910 uid=0 auid=4294967295 ses=4294967295 msg='op=device-disconnect interface="wlan0" ifindex=3 pid=121138 uid=1000 result=success exe=>
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.2977] audit: op="device-disconnect" interface="wlan0" ifindex=3 pid=121138 uid=1000 result="success"
Aug 29 12:11:58 Sussyamug dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1>
Aug 29 12:11:58 Sussyamug kernel: audit: type=1111 audit(1661767918.293:157): pid=910 uid=0 auid=4294967295 ses=4294967295 msg='op=device-disconnect interface="wlan0" ifindex=3 pid=121138 >
Aug 29 12:11:58 Sussyamug systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug 29 12:11:58 Sussyamug dbus-daemon[908]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 29 12:11:58 Sussyamug systemd[1]: Started Network Manager Script Dispatcher Service.
Aug 29 12:11:58 Sussyamug audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? ad>
Aug 29 12:11:58 Sussyamug kernel: audit: type=1130 audit(1661767918.307:158): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/sy>
Aug 29 12:11:58 Sussyamug kernel: wlan0: deauthenticating from 00:d7:8f:e6:45:ed by local choice (Reason: 3=DEAUTH_LEAVING)
Aug 29 12:11:58 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:d7:8f:e6:45:ed reason=3 locally_generated=1
Aug 29 12:11:58 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.4473] device (wlan0): supplicant interface state: completed -> disconnected
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.4473] device (p2p-dev-wlan0): supplicant management interface state: completed -> disconnected
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.4476] device (wlan0): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.4728] dhcp4 (wlan0): canceled DHCP transaction
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.4728] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.4729] dhcp4 (wlan0): state changed no lease
Aug 29 12:11:58 Sussyamug wpa_supplicant[1148]: wlan0: PMKSA-CACHE-REMOVED 00:d7:8f:e6:45:ed 0
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.4946] device (wlan0): set-hw-addr: set MAC address to 5A:3C:B7:CA:41:82 (scanning)
Aug 29 12:11:58 Sussyamug NetworkManager[910]: <info>  [1661767918.5057] manager: NetworkManager state is now DISCONNECTED
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0048] device (wlan0): Activation: starting connection 'Next' (6659d7e9-d62c-4890-b6f2-1a5a595e3c6e)
Aug 29 12:12:04 Sussyamug kernel: audit: type=1111 audit(1661767924.000:159): pid=910 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=6659d7e9-d62c-4890-b6f2-1a5a595e>
Aug 29 12:12:04 Sussyamug audit[910]: USYS_CONFIG pid=910 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=6659d7e9-d62c-4890-b6f2-1a5a595e3c6e name="Next" pid=121138 >
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0052] audit: op="connection-activate" uuid="6659d7e9-d62c-4890-b6f2-1a5a595e3c6e" name="Next" pid=121138 uid=1000 result=>
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0054] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0058] manager: NetworkManager state is now CONNECTING
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0379] device (wlan0): set-hw-addr: reset MAC address to C8:E2:65:0E:6A:82 (preserve)
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0397] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0400] device (wlan0): Activation: (wifi) access point 'Next' has security, but secrets are required.
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0400] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0417] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0420] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0422] device (wlan0): Activation: (wifi) connection 'Next' has security, and secrets exist.  No new secrets needed.
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0423] Config: added 'ssid' value 'Next'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0423] Config: added 'scan_ssid' value '1'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0423] Config: added 'bgscan' value 'simple:30:-65:300'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0423] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0423] Config: added 'auth_alg' value 'OPEN'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0423] Config: added 'password' value '<hidden>'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0424] Config: added 'eap' value 'FAST PEAP'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0424] Config: added 'fragment_size' value '1266'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0424] Config: added 'phase1' value 'fast_provisioning=1'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0424] Config: added 'pac_file' value 'blob://pac-blob-6659d7e9-d62c-4890-b6f2-1a5a595e3c6e'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0424] Config: added 'identity' value 'carl2792'
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0424] Config: added 'proactive_key_caching' value '1'
Aug 29 12:12:04 Sussyamug kdeconnectd[121122]: "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/5”"
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: SME: Trying to authenticate with 00:d7:8f:c9:54:2d (SSID='Next' freq=5640 MHz)
Aug 29 12:12:04 Sussyamug kernel: wlan0: authenticate with 00:d7:8f:c9:54:2d
Aug 29 12:12:04 Sussyamug kernel: wlan0: Invalid HE elem, Disable HE
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0724] device (wlan0): supplicant interface state: disconnected -> authenticating
Aug 29 12:12:04 Sussyamug kernel: wlan0: send auth to 00:d7:8f:c9:54:2d (try 1/3)
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.0725] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> authenticating
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: Trying to associate with 00:d7:8f:c9:54:2d (SSID='Next' freq=5640 MHz)
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.1010] device (wlan0): supplicant interface state: authenticating -> associating
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.1010] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Aug 29 12:12:04 Sussyamug kernel: wlan0: authenticated
Aug 29 12:12:04 Sussyamug kernel: wlan0: associate with 00:d7:8f:c9:54:2d (try 1/3)
Aug 29 12:12:04 Sussyamug kernel: wlan0: RX AssocResp from 00:d7:8f:c9:54:2d (capab=0x11 status=0 aid=21)
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: Associated with 00:d7:8f:c9:54:2d
Aug 29 12:12:04 Sussyamug kernel: wlan0: associated
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.1215] device (wlan0): supplicant interface state: associating -> associated
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.1216] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=Nextdc1.next.local' hash=9fe4ebf859d4ddc17e0f91874a38268dd214f024587c2c9fda7fbf269d5b7c>
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:Nextdc1.next.local
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=Nextdc1.next.local' hash=9fe4ebf859d4ddc17e0f91874a38268dd214f024587c2c9fda7fbf269d5b7c>
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:Nextdc1.next.local
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=Nextdc1.next.local' hash=9fe4ebf859d4ddc17e0f91874a38268dd214f024587c2c9fda7fbf269d5b7c>
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:Nextdc1.next.local
Aug 29 12:12:04 Sussyamug kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 00:d7:8f:c9:54:2d
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: EAP-MSCHAPV2: Authentication succeeded
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
Aug 29 12:12:04 Sussyamug kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 00:d7:8f:c9:54:2d
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: EAP-MSCHAPV2: Authentication succeeded
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: PMKSA-CACHE-ADDED 00:d7:8f:c9:54:2d 0
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: WPA: Key negotiation completed with 00:d7:8f:c9:54:2d [PTK=CCMP GTK=CCMP]
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:d7:8f:c9:54:2d completed [id=0 id_str=]
Aug 29 12:12:04 Sussyamug kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.2798] device (wlan0): supplicant interface state: associated -> completed
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.2799] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Next"
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.2799] device (p2p-dev-wlan0): supplicant management interface state: associated -> completed
Aug 29 12:12:04 Sussyamug wpa_supplicant[1148]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=26000
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.2801] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.2807] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.4166] dhcp4 (wlan0): state changed new lease, address=10.78.66.121
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.4172] policy: set 'Next' (wlan0) as default for IPv4 routing and DNS
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.4348] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.4374] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.4377] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.4381] manager: NetworkManager state is now CONNECTED_SITE
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.4393] device (wlan0): Activation: successful, device activated.
Aug 29 12:12:04 Sussyamug NetworkManager[910]: <info>  [1661767924.4400] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 29 12:12:08 Sussyamug systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

I don't know much about wifi and the protocols which it use. But when it succesfully connects in the log it says:

Config: added 'eap' value 'FAST PEAP'

Compared to now when it fails, it only says "FAST":

Config: added 'eap' value 'FAST'

progandy · 2022-09-09 18:55:40

seth wrote:

You have one EAP failure on bssid=00:d7:8f:34:b1:ed
Sep 08 12:05:50 Sussyamug wpa_supplicant[1179]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
Sep 08 12:05:50 Sussyamug wpa_supplicant[1179]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 -> NAK
Sep 08 12:05:50 Sussyamug wpa_supplicant[1179]: wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
Since there's only 25 tried and the other side doesn't like that you maybe need a different method? TLS or TTLS next to PEAP?

Isn't it the AP that requests method 25 (peap) and wpa_supplicant rejects it with NAK? That matches with the difference between failing (EAP FAST) and succeeding (EAP FAST PEAP) logs given by Sveske-juice.

Sveske-juice, you should probably make sure that your profile has the eap method set to PEAP. As I don't use networkmanager, I can't really help with that.

Last edited by progandy (2022-09-09 18:56:29)

seth · 2022-09-09 20:06:12

progandy wrote:

Isn't it the AP that requests method 25 (peap) and wpa_supplicant rejects it with NAK? That matches with the difference between failing (EAP FAST) and succeeding (EAP FAST PEAP) logs given by Sveske-juice.

Quite possible and yes, absolutely.

seth wrote:

What does your connection file look like (you can of course obfuscate the private stuff)?

Sveske-juice · 2022-09-12 08:29:08

I found the solution to the problem. The reason why it didn't work was because it was using EAP FAST i think.

Solved it by deleting the connection from Advanced Network Configuration gui app. And trying to connect to the network again and specifying peap.

Last edited by Sveske-juice (2022-09-12 08:29:55)

seth · 2022-09-12 11:11:47

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Sveske-juice · 2022-09-13 11:44:29

Marked solved now :)

Arch Linux

#1 2022-09-08 10:46:10

[SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#2 2022-09-08 11:42:12

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#3 2022-09-08 14:02:19

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#4 2022-09-09 15:09:44

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#5 2022-09-09 16:09:13

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#6 2022-09-09 17:13:34

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#7 2022-09-09 18:55:40

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#8 2022-09-09 20:06:12

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#9 2022-09-12 08:29:08

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#10 2022-09-12 11:11:47

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

#11 2022-09-13 11:44:29

Re: [SOLVED] Can't connect to school network anymore (WPA 2 enterprise)

Board footer