latin-1 / um5302ta

17 stars 4 forks source link

Some Wifi networks don't work #2

Open akoidan opened 1 year ago

akoidan commented 1 year ago

Hey,

Did you issues that some wifi networks when you connect as a client. Some of them work and some? devices in this networks can't be ping and internet don't work. I can't find a factor that causes a wifi network to not working. Sometimes it connect

E.g. one of the caffe's networks (SSID TerraMare) don't work from my laptop, but works perfectly from a mobile device or any other friend's devices (or windows from this laptop).

[  537.399513] audit: type=1111 audit(1671361570.283:112): pid=635 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=0152b7be-0939-47b1-b2c0-9e3849bc5865 name="TerraMare" pid=825 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  537.539487] wlan0: authenticate with 66:d1:54:38:a1:8a
[  537.581542] wlan0: send auth to 66:d1:54:38:a1:8a (try 1/3)
[  537.614430] wlan0: authenticated
[  537.620033] wlan0: associate with 66:d1:54:38:a1:8a (try 1/3)
[  537.718137] wlan0: RX AssocResp from 66:d1:54:38:a1:8a (capab=0x401 status=0 aid=6)
[  537.752731] wlan0: associated
[  537.899931] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  542.429410] audit: type=1131 audit(1671361575.313:113): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  564.615365] audit: type=1130 audit(1671361597.501:114): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  574.618394] audit: type=1131 audit(1671361607.504:115): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 18 13:18:38 zenbook wpa_supplicant[636]: wlan0: CTRL-EVENT-DISCONNECTED bssid=de:1d:85:b2:a8:34 reason=3 locally_generated=1
Dec 18 13:18:38 zenbook wpa_supplicant[636]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 18 13:18:38 zenbook wpa_supplicant[636]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 18 13:18:38 zenbook wpa_supplicant[636]: wlan0: Reject scan trigger since one is already pending
Dec 18 13:18:38 zenbook wpa_supplicant[636]: wlan0: Failed to initiate AP scan
Dec 18 13:18:39 zenbook wpa_supplicant[636]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 18 13:18:39 zenbook wpa_supplicant[636]: wlan0: Reject scan trigger since one is already pending
Dec 18 13:18:39 zenbook wpa_supplicant[636]: wlan0: Failed to initiate AP scan
Dec 18 13:18:40 zenbook wpa_supplicant[636]: wlan0: Reject scan trigger since one is already pending
Dec 18 13:18:40 zenbook wpa_supplicant[636]: wlan0: Failed to initiate AP scan
Dec 18 13:18:44 zenbook wpa_supplicant[636]: wlan0: SME: Trying to authenticate with ce:2d:e0:ea:4b:9e (SSID='TerraMare' freq=2412 MHz)
Dec 18 13:18:44 zenbook wpa_supplicant[636]: wlan0: Trying to associate with ce:2d:e0:ea:4b:9e (SSID='TerraMare' freq=2412 MHz)
Dec 18 13:18:44 zenbook wpa_supplicant[636]: wlan0: Associated with ce:2d:e0:ea:4b:9e
Dec 18 13:18:44 zenbook wpa_supplicant[636]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dec 18 13:18:44 zenbook wpa_supplicant[636]: wlan0: WPA: Key negotiation completed with ce:2d:e0:ea:4b:9e [PTK=CCMP GTK=CCMP]
Dec 18 13:18:44 zenbook wpa_supplicant[636]: wlan0: CTRL-EVENT-CONNECTED - Connection to ce:2d:e0:ea:4b:9e completed [id=0 id_str=]
Dec 18 13:18:44 zenbook wpa_supplicant[636]: bgscan simple: Failed to enable signal strength monitoring

But I can't access anything in the network, even can't ping the router.

Some authorization with that networks times out and it can't connect like in this thread

Some networks work smoothly.

I tried switching from wpa_supplicant to iwd but it didn't help.

My system: Asus Zenbook s13 UM5302TA.310 WIfi card: MT7922 802.11ax Archlinux bleeding edge KDE + Network manager. All packages defaulted Kernel from this repo.

latin-1 commented 1 year ago

I've never had the problem you describe. Perhaps you should consider replacing the MT7922 with an AX200/AX210. 😢

winstonma commented 1 year ago

@akoidan Yes I had the same experience. But I am not sure if we face the same situation.

I also went to a cafe with the public wifi. After the connection is successful there is no connection prompt page pop out. After checking ifconfigI found that the assigned IP is totally wrong (I got 172.X.X.X but my phone got 192.X.X.X). It only happen with kernel 6.2+.

After rebooting my laptop and select 6.1.X kernel, the assigned IP is correct. Still up to date I didn't know why and also I didn't check all 6.2 and 6.3 kernel so I am not sure what causes the problem.

But based on your post date I guess you were not using kernel 6.2+ so I am not sure we got the same problem. Also I guess you can boot using the kernel that comes with the original linux release, and see if that helps.

Kernel 6.1 (Correct IP address)

$ uname -r
6.1.34-060134-generic

$ ifconfig wlp1s0
wlp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.101.47  netmask 255.255.254.0  broadcast 192.168.101.255
        inet6 fe80::f3f2:7146:5b7e:f7dc  prefixlen 64  scopeid 0x20<link>
        ether 56:50:21:49:01:41  txqueuelen 1000  (Ethernet)
        RX packets 1714  bytes 114219 (114.2 KB)
        RX errors 0  dropped 14  overruns 0  frame 0
        TX packets 1013  bytes 140684 (140.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Kernel 6.3 (Wrong IP address)

$ uname -r
6.3.7-060307-generic

$ ifconfig wlp1s0
wlp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.30.24.24  netmask 255.255.255.0  broadcast 172.30.24.255
        inet6 fe80::f3f2:7146:5b7e:f7dc  prefixlen 64  scopeid 0x20<link>
        ether 56:58:a9:43:f1:d8  txqueuelen 1000  (Ethernet)
        RX packets 2124  bytes 462512 (462.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2527  bytes 371540 (371.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Both are connecting to the same access point but got different IP ranges. Kernel 6.1 got the correct IP address but Kernel 6.3 got the wrong address. And due to the wrong assigned IP the public wifi login page didn't show up.

@latin-1 Did you replace MT7922?

winstonma commented 1 year ago

@akoidan I find an old Intel 8265 wifi card from my old laptop and replaced the Wifi card.

Seems my laptop wifi connectivity and the network speed is more stable now. Hope all those weird behavior would gone. Just wonder if the laptop would have better wifi connectivity by replacing Intel 8265 with Intel AX200/AX210.