You are not logged in.
Yesterday I updated Arch Linux for the first time in 3 months.
I am also using an Intel AX200 network card.
I used to share my LTE network with AX200.
Also at this time I am using these pages to set up masquerading and forwarding for nftables.
https://wiki.archlinux.org/title/Internet_sharing
https://wiki.archlinux.org/title/Networ … over_Wi-Fi
However, after updating and rebooting, I am no longer able to share.
Please help.
Last edited by 04tm34l (2022-04-17 11:46:06)
Offline
Yesterday I updated Arch Linux for the first time in 3 months.
What were you doing? Hibernating during the winter?
I am also using an Intel AX200 network card.
I used to share my LTE network with AX200.
Also at this time I am using these pages to set up masquerading and forwarding for nftables.https://wiki.archlinux.org/title/Internet_sharing
https://wiki.archlinux.org/title/Networ … over_Wi-FiHowever, after updating and rebooting, I am no longer able to share.
Is this the same arch box as in your other (resolv.conf) thread?
Do you try to setup the sharing after the update or did it already work before the update?
Offline
What were you doing? Hibernating during the winter?
I just didn't update it for a long time because I was back home for the winter.
Is this the same arch box as in your other (resolv.conf) thread?
Yes.
Do you try to setup the sharing after the update or did it already work before the update?
Before the update I could share normally. However, after the update, it is in hotspot mode but cannot connect to the network from other devices.
Offline
Just to clarify:
You use your LTE network as your main internet connection?
You use your WiFi card exclusively as a Software access point for other devices around you?
Offline
I mainly use its LTE network.
I also use the Wi-Fi card as an access point most of the time, but also as a client.
Offline
I also use the Wi-Fi card as an access point most of the time, but also as a client.
Simultaneously? Or do you switch between sharing and client?
And after the update only sharing doesn't work?
Offline
Switch between client and shared use.
Only the share has stopped working.
Offline
How do you exactly switch between sharing and client?
Did you re-check all critical points of the Wiki article:
- Does the driver still support "AP" mode?
- Is /etc/hostapd/hostapd.conf still correct and are the devices up when sharing is active?
- Is the WiFi device still unmanaged?
- Is the NAT setup still valid?
Offline
Did you re-check all critical points of the Wiki article:
- Does the driver still support "AP" mode?
- Is /etc/hostapd/hostapd.conf still correct and are the devices up when sharing is active?
- Is the WiFi device still unmanaged?
- Is the NAT setup still valid?
Everything was fine. Also tried hostapd, no change.
I did find out one thing during this time.
I mainly use Xiaomi Mi MIX 2 smartphone with LineageOS which is a custom ROM.
Other Xiaomi Mi MIX 2S are LineageOS as well, but even with these I could not get a connection.
However, my Xiaomi Mi MIX 3 with GSI's Pixel Experience was able to connect.
I am more and more confused, but maybe it is LineageOS that has the problem.
Perhaps I should close this post?
Offline
However, should I report this as a problem to NetworkManager because the LineageOS version is 18.1 (Android 11), the same as 3 months ago, and my Android TV Box (Android 10) can no longer connect.
Offline
Did you try an older kernel? Maybe there was a change in the wifi driver.
And what exactly is the problem? Can your phone connect to the wifi, but not access the internet or does the wifi connection itself fail?
Last edited by progandy (2022-04-13 10:06:43)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
I tried the lts kernel, but no luck.
Clarify the issue.
When starting a hotspot with WPA-PSK from NetworkManager, some devices will not be able to connect.
I think it comes down to this.
Offline
I mainly use Xiaomi Mi MIX 2 smartphone with LineageOS which is a custom ROM.
Other Xiaomi Mi MIX 2S are LineageOS as well, but even with these I could not get a connection.
However, my Xiaomi Mi MIX 3 with GSI's Pixel Experience was able to connect.I am more and more confused, but maybe it is LineageOS that has the problem.
So the AP principally works, but discriminatively.
Did you check/compare the logs for the different phones?
Do the failing approaches show up at all?
What are the symptoms/error messages on the phone reg. the connection failure?
Offline
Looking at the log of the device (Mi MIX 2) that cannot connect, wpa_supplicant is giving a reason=3 error.
Offline
DEAUTH_LEAVING can have all sorts of causes - do you have more log for context?
Offline
I share my Mi MIX 2 bug report on a file sharing site called firestorage.
This site can be viewed in both Japanese and English, but in English I have to register my e-mail address, so it is in Japanese only, but you will not get lost in using it.
Shared link was removed.
The access point used for the test is the SSID "test_nomap".
I apologize for any inconvenience.
Last edited by 04tm34l (2022-04-17 04:02:44)
Offline
Sorting through the log a bit, this matches wpa|test_nomap
04-14 09:16:22.433 wifi 8146 8146 I wpa_supplicant: nl80211: deinit ifname=p2p0 disabled_11b_rates=0
04-14 09:16:22.488 wifi 8146 8146 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=a8:7e:ea:ee:f5:20 reason=3 locally_generated=1
04-14 09:16:22.497 wifi 8146 8146 I wpa_supplicant: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
04-14 09:16:22.521 wifi 8146 8146 I wpa_supplicant: Terminating...
04-14 09:46:17.765 root 0 0 I init : starting service 'wpa_supplicant'...
04-14 09:46:17.766 root 0 0 I init : Created socket '/dev/socket/wpa_wlan0', mode 660, user 1010, group 1010
04-14 09:46:17.878 root 0 0 I : R0: [wpa_supplicant][700343133] [09:46:17.878870] wlan: [4133:I :HDD] 00000000: 7f 0a 00 00 0a 82 00 40 00 00 00 01 ff 03 02 00
04-14 09:46:17.878 root 0 0 I : R0: [wpa_supplicant][700343446] [09:46:17.878886] wlan: [4133:I :HDD] 00000010: ff dd 0a 50 6f 9a 16 03 01 03 65 01 01 dd 08 8c
04-14 09:46:17.878 root 0 0 I : R0: [wpa_supplicant][700343577] [09:46:17.878892] wlan: [4133:I :HDD] 00000020: fd f0 01 01 02 01 00
04-14 09:46:17.981 root 0 0 I : R0: [wpa_supplicant][702317260] [09:46:17.981689] wlan: [4133:I :HDD] 00000000: 7f 0a 00 00 0a 82 00 40 00 00 00 01 ff 03 02 00
04-14 09:46:17.981 root 0 0 I : R0: [wpa_supplicant][702317658] [09:46:17.981709] wlan: [4133:I :HDD] 00000010: ff dd 0a 50 6f 9a 16 03 01 03 65 01 01 dd 08 8c
04-14 09:46:17.981 root 0 0 I : R0: [wpa_supplicant][702317814] [09:46:17.981717] wlan: [4133:I :HDD] 00000020: fd f0 01 01 02 01 00
04-14 09:46:17.994 root 0 0 I : R0: [wpa_supplicant][702557847] [09:46:17.994219] wlan: [4133:I :HDD] 00000000: 7f 0a 00 00 0a 82 00 40 00 00 00 01 ff 03 02 00
04-14 09:46:17.994 root 0 0 I : R0: [wpa_supplicant][702558235] [09:46:17.994239] wlan: [4133:I :HDD] 00000010: ff dd 0a 50 6f 9a 16 03 01 02 65 01 01 dd 08 8c
04-14 09:46:17.994 root 0 0 I : R0: [wpa_supplicant][702558385] [09:46:17.994247] wlan: [4133:I :HDD] 00000020: fd f0 01 01 02 01 00
04-14 09:46:18.092 root 0 0 I : R0: [wpa_supplicant][704435432] [09:46:18.092010] wlan: [4133:I :HDD] 00000000: 7f 0a 00 00 0a 02 00 40 00 00 00 01 ff 03 02 00
04-14 09:46:18.092 root 0 0 I : R0: [wpa_supplicant][704435816] [09:46:18.092030] wlan: [4133:I :HDD] 00000010: ff dd 0a 50 6f 9a 16 03 01 03 65 01 01 dd 08 8c
04-14 09:46:18.092 root 0 0 I : R0: [wpa_supplicant][704435970] [09:46:18.092038] wlan: [4133:I :HDD] 00000020: fd f0 01 01 02 01 00
04-14 09:46:54.856 1000 1391 2049 E WifiConfigManager: Cannot find network with networkId -1 or configKey "test_nomap"WPA_PSK
04-14 09:46:54.856 1000 1391 2049 E WifiConfigManager: Cannot find network with networkId -1 or configKey "test_nomap"WPA_PSK
04-14 09:46:54.892 1000 1391 2049 E WifiConfigManager: Cannot find network with configKey "test_nomap"WPA_PSK
04-14 09:46:54.897 1000 1391 2049 D WifiConfigManager: Enable disabled network: "test_nomap" num=0
04-14 09:46:54.966 1000 1391 2049 D WifiConfigManager: Enable disabled network: "test_nomap" num=0
04-14 09:46:55.069 1000 1391 2049 D WifiClientModeImpl: ConnectedMacRandomization SSID(test_nomap). setMacAddress(a2:34:70:42:dd:45) from 7a:ea:f7:9d:04:9c = true
04-14 09:46:55.078 root 0 0 I : R0: [wpa_supplicant][1414567646] [09:46:55.078067] wlan: [4133:I :HDD] 00000000: 7f 0a 00 00 0a 82 00 40 00 00 00 01 ff 03 02 00
04-14 09:46:55.078 root 0 0 I : R0: [wpa_supplicant][1414568059] [09:46:55.078088] wlan: [4133:I :HDD] 00000010: ff dd 0a 50 6f 9a 16 03 01 02 65 01 01 dd 08 8c
04-14 09:46:55.078 root 0 0 I : R0: [wpa_supplicant][1414568216] [09:46:55.078096] wlan: [4133:I :HDD] 00000020: fd f0 01 01 02 01 00
04-14 09:46:55.079 1000 1391 2049 D SupplicantStaIfaceHal: connectToNetwork "test_nomap"SAE
04-14 09:46:58.103 1000 1391 2049 D SupplicantStaIfaceHal: connectToNetwork "test_nomap"SAE
04-14 09:46:59.973 1000 1391 2049 D WifiConfigManager: Enable disabled network: "test_nomap" num=0
04-14 09:47:07.460 1000 1391 2049 D SupplicantStaIfaceHal: connectToNetwork "test_nomap"SAE
04-14 09:47:22.153 root 0 0 I init : Service 'wpa_supplicant' (pid 4133) exited with status 0 oneshot service took 64.385002 seconds in background
04-14 09:47:22.153 root 0 0 I init : Sending signal 9 to service 'wpa_supplicant' (pid 4133) process group...
So the local_choice disconnect is very early on and seems related to toggling the airplane mode.
Later you actually do connect to the test_nomap SSID, but the only response to that is
04-14 09:47:07.463 wifi 739 4120 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0x6a
…
04-14 09:47:08.754 10175 9816 9920 W System.err: java.net.UnknownHostException: Unable to resolve host "acs.m.taobao.com": No address associated with hostname
No idea whether the UnknownHostException is relevant here - or how the system intends to resolve that host w/o a network or whether that's the connectivity test (obvisouly failing)… :\
Offline
Does that mean there is nothing I can do about it?
Offline
It means I suspect your phone - at least the logs don't suggest an effort to associate w/ the AP (though it seems to be found)
And the logs are *VAST*, so I'd expect to see "something™" in there (but that's speculative)
Do the Lineage phones connect fine to other APs? Do you have a log that covers a succesful and unsuccesful attempt for comparism?
Offline
I shared the bug report on firestorage as I did yesterday.
Shared link was removed
Note that the SSID that successfully connected is "MIX 2S Jade Art Green Edition" and the one that failed is "test_nomap".
Last edited by 04tm34l (2022-04-17 04:02:14)
Offline
Those logs are really messy
But one thing that stuck out to me was grepping for PSK…
04-15 19:47:20.369 1000 1400 2002 E WifiConfigManager: Cannot find network with networkId -1 or configKey "test_nomap"WPA_PSK
04-15 19:47:20.369 1000 1400 2002 E WifiConfigManager: Cannot find network with networkId -1 or configKey "test_nomap"WPA_PSK
04-15 19:47:20.404 1000 1400 2002 E WifiConfigManager: Cannot find network with configKey "test_nomap"WPA_PSK
application/pskc+xml:
rec[2]: time=04-15 19:47:52.210 processed=ConnectModeState org=DisconnectedState dest=<null> what=CMD_START_CONNECT screen=on 6 1010 targetConfigKey="test_nomap"WPA_PSK BSSID=null targetBssid=any roam=false
…
rec[85]: time=04-15 19:49:52.716 processed=ConnectModeState org=DisconnectedState dest=<null> what=CMD_START_CONNECT screen=on 6 1010 targetConfigKey="test_nomap"WPA_PSK BSSID=null targetBssid=any roam=false
2022-04-07T16:55:02.199 - setNetworkSelectionEnabled: configKey="MIX 2S Jade Art Green Edition"WPA_PSK old networkStatus=NETWORK_SELECTION_PERMANENTLY_DISABLED disableReason=NETWORK_SELECTION_DISABLED_NO_INTERNET_PERMANENT
2022-04-07T16:55:02.201 - setNetworkSelectionStatus: configKey="MIX 2S Jade Art Green Edition"WPA_PSK networkStatus=NETWORK_SELECTION_ENABLED disableReason=NETWORK_SELECTION_ENABLE
2022-04-15T19:47:00.245 - setNetworkSelectionStatus: configKey="MIX 2S Jade Art Green Edition"WPA_PSK networkStatus=NETWORK_SELECTION_ENABLED disableReason=NETWORK_SELECTION_ENABLE
2022-04-15T19:47:20.404 - addOrUpdateNetworkInternal: added/updated config. netId=6 configKey="test_nomap"WPA_PSK uid=1000 name=android.uid.system:1000
2022-04-15T19:47:20.430 - setNetworkSelectionEnabled: configKey="test_nomap"WPA_PSK old networkStatus=NETWORK_SELECTION_PERMANENTLY_DISABLED disableReason=NETWORK_SELECTION_DISABLED_BY_WIFI_MANAGER
2022-04-15T19:47:20.431 - setNetworkSelectionStatus: configKey="test_nomap"WPA_PSK networkStatus=NETWORK_SELECTION_ENABLED disableReason=NETWORK_SELECTION_ENABLE
2022-04-15T19:47:33.407 - addOrUpdateNetworkInternal: added/updated config. netId=6 configKey="test_nomap"WPA_PSK uid=1000 name=android.uid.system:1000
2022-04-15T19:47:33.428 - setNetworkSelectionStatus: configKey="test_nomap"WPA_PSK networkStatus=NETWORK_SELECTION_ENABLED disableReason=NETWORK_SELECTION_ENABLE
2022-04-15T19:47:36.578 - setNetworkSelectionStatus: configKey="test_nomap"WPA_PSK networkStatus=NETWORK_SELECTION_ENABLED disableReason=NETWORK_SELECTION_ENABLE
2022-04-15T19:47:39.647 - setNetworkSelectionStatus: configKey="test_nomap"WPA_PSK networkStatus=NETWORK_SELECTION_ENABLED disableReason=NETWORK_SELECTION_ENABLE
KeyMgmt: WPA_PSK Protocols: WPA RSN
PSK/SAE: *
…
KeyMgmt: WPA_PSK Protocols: WPA RSN
PSK/SAE: *
2432 -35 206.135 MIX 2S Jade Art Green Edition [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS]
2462 -53 205.933 AG20R-96D450 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2412 -55 206.257 test_nomap [WPA2-PSK-CCMP+TKIP][RSN-PSK+PSK-SHA256+SAE+FT/SAE-CCMP+TKIP][WPA-PSK-CCMP+TKIP][ESS][WPS]
2452 -58 206.000 Buffalo-G-2430 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
5220 -59 206.070 Buffalo-A-2430 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2422 -68 206.197 603hwa-40e5d5 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
5180 -69 206.244 AG20R-96D450-5G [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2452 -74 205.996 BC1AE460B3A5-2G [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
2462 -79 205.944 A8989274A9D7-2G [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
5540 -80 205.435 A8989274A9D7-5G [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
5500 -82 205.574 HR01b-01763B [WPA2-PSK-CCMP][RSN-PSK+SAE-CCMP][ESS][WPS]
2462 -82 205.961 e-timer-7BF5F0 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2437 -82 206.078 aterm-c98da7-g [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
2412 -55 206.260 test_nomap [WPA2-PSK-CCMP+TKIP][RSN-PSK+PSK-SHA256+SAE+FT/SAE-CCMP+TKIP][WPA-PSK-CCMP+TKIP][ESS][WPS]
2422 -68 206.200 603hwa-40e5d5 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
5180 -69 206.247 AG20R-96D450-5G [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2432 -35 206.138 MIX 2S Jade Art Green Edition [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS]
5220 -59 206.073 Buffalo-A-2430 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2452 -58 206.003 Buffalo-G-2430 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2462 -53 205.936 AG20R-96D450 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
5500 -82 205.577 HR01b-01763B [WPA2-PSK-CCMP][RSN-PSK+SAE-CCMP][ESS][WPS]
5540 -80 205.438 A8989274A9D7-5G [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
2462 -79 205.947 A8989274A9D7-2G [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
2462 -82 205.964 e-timer-7BF5F0 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2462 -81 215.599 elecom2g-7BF5F0 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2437 -82 206.081 aterm-c98da7-g [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
2452 -74 205.999 BC1AE460B3A5-2G [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
5560 -85 207.283 elecom5g-7BF5F0 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2412 -49 38.401 test_nomap [WPA2-PSK-CCMP+TKIP][RSN-PSK+PSK-SHA256+SAE+FT/SAE-CCMP+TKIP][WPA-PSK-CCMP+TKIP][ESS][WPS]
2422 -67 44.828 603hwa-40e5d5 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
5180 -68 44.866 AG20R-96D450-5G [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2432 -35 38.261 MIX 2S Jade Art Green Edition [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS]
5220 -61 44.687 Buffalo-A-2430 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2452 -59 44.629 Buffalo-G-2430 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2462 -56 57.455 AG20R-96D450 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
5500 -81 50.645 HR01b-01763B [WPA2-PSK-CCMP][RSN-PSK+SAE-CCMP][ESS][WPS]
5540 -81 44.056 A8989274A9D7-5G [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
2462 -79 44.537 A8989274A9D7-2G [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
2462 -80 44.559 e-timer-7BF5F0 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2462 -84 44.569 elecom2g-7BF5F0 [WPA2-PSK-CCMP][RSN-PSK-CCMP][ESS][WPS]
2447 -73 44.684 HR01a-01763A [WPA2-PSK-CCMP][RSN-PSK+SAE-CCMP][ESS][WPS]
2452 -74 44.658 BC1AE460B3A5-2G [WPA2-PSK-CCMP][RSN-PSK-CCMP][WPA-PSK-CCMP][ESS][WPS]
One of the APs is not like the other children…
https://wiki.archlinux.org/title/Softwa … figuration
Offline
Thank you seth for simplifying that big report so much.
I ended up disabling RSN and using only WPA (not WPA2) and now I can connect. Until now I had to hide the SSID without a password. Now I can share my network with peace of mind
Also, should I report this to the NetworkManager team?
Last edited by 04tm34l (2022-04-17 00:37:29)
Offline
I'm not sure who's responsible for the hostap config in your case, but if it happened through some NM GUI clickthrough wizard, then yes.
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.
Edit: the primal difference looks like TKIP, though.
Last edited by seth (2022-04-17 06:42:33)
Offline
Apart from TKIP, Networkmanager also seems to enable WPA2/WPA3 compatibility mode, maybe your devices don't like that or WPA-PSK-SHA256.
You should probably try to reproduce the problem with hostapd and then make minimal changes to the configuration to make it work again. Then you know what the problem is with the networkmanager and you can write a good bug report.
Last edited by progandy (2022-04-17 07:24:33)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
I can't say for sure because hostapd doesn't work well in my environment and even the SSID doesn't appear on other devices (I don't have the energy to deal with this anymore). But I think the problem is probably WPA-PSK-SHA256, not TKIP. Currently I was able to reproduce the problem by enabling or disabling RSN in nmcli.
Thanks so much to -thc, progandy, and seth, for replying this time.
Offline