Can't connect to new Wifi Networks (Intel AC 8265). Old connections are doing fine

I’m unable to join new Wi-Fi networks with my current installation of Tumbleweed. I have noticed this behaviour from a long time, but I was certain it was a bug regarding an Eduroam connection. However, I have noticed that the only Wi-Fi networks I am allowed to connect are the ones I have connected to during my first days with this installation (end of 2022).

I’m using a ThinkPad T470 with an Intel Dual Band Wireless AC 8265 network card, having the last updates (just upgraded the distro today), and using Gnome 43 and Network Manager.
Expected behaviour is to select a network, insert the password, and connect to it.
Current behaviour: I select the desired network, insert the password, and have an infinite prompts to confirm my password (despite being correct).

Thank you all in advance for any tip or solution for this issue.

Hi, welcome to the forum!

Do you see the networks you want to connect to. On the command line you can get a list of networks using:

$ sudo iwlist wlp0s20u10 scanning | grep -P ‘ESSID:’

Replace wlp0s20u10 by the interface of your card (try “sudo iwconfig”)

Next start on the command line “sudo journalctl -f” and try connecting using the network manager to one of the networks you like to connect to. journalctl should give some information on what is going on and likely some hints on what is going wrong.

Stop journalctl by pressing Ctrl-C and copy the log. Replace/remove from the log things that you want to keep private and share the log here.

If it is not too long (about 30 lines) paste it in your message, select it and press Ctrl+E to make it preformatted text. If it is longer you can use https://paste.opensuse.org/

1 Like

Hello, thank you for the warm welcome!

I was unable to reproduce the command you listed (even after the alteration for the interface on my card), however, I ran tail -f /var/log/wpa_supplicant.log as sudo which gave me the following output (note that I masked the SSID)

1684247776.707514: wlp4s0: SME: Trying to authenticate with bc:26:c7:c5:2a:8f (SSID='HIDDEN' freq=5260 MHz)
1684247776.721034: wlp4s0: Trying to associate with bc:26:c7:c5:2a:8f (SSID='HIDDEN' freq=5260 MHz)
1684247776.738776: wlp4s0: Associated with bc:26:c7:c5:2a:8f
1684247776.739866: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
1684247776.741876: wlp4s0: CTRL-EVENT-EAP-STARTED EAP authentication started
1684247800.898148: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=bc:26:c7:c5:2a:8f reason=3 locally_generated=1
1684247800.898661: nl80211: Failed to open /proc/sys/net/ipv4/conf/wlp4s0/drop_unicast_in_l2_multicast: Read-only file system
1684247800.898745: nl80211: Failed to set IPv4 unicast in multicast filter
1684247800.899087: nl80211: Failed to open /proc/sys/net/ipv4/conf/wlp4s0/drop_unicast_in_l2_multicast: Read-only file system
1684247800.899151: nl80211: Failed to set IPv4 unicast in multicast filter
1684247800.899217: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
1684247804.067339: wlp4s0: SME: Trying to authenticate with bc:26:c7:c5:2a:8f (SSID='HIDDEN' freq=5260 MHz)
1684247804.093103: wlp4s0: Trying to associate with bc:26:c7:c5:2a:8f (SSID='HIDDEN' freq=5260 MHz)
1684247804.101556: wlp4s0: Associated with bc:26:c7:c5:2a:8f
1684247804.101927: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
1684247804.114459: wlp4s0: CTRL-EVENT-EAP-STARTED EAP authentication started
1684247813.363366: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=bc:26:c7:c5:2a:8f reason=23
1684247813.363506: wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HIDDEN" auth_failures=1 duration=10 reason=AUTH_FAILED
1684247813.363594: BSSID bc:26:c7:c5:2a:8f ignore list count incremented to 2, ignoring for 10 seconds
1684247813.364064: nl80211: Failed to open /proc/sys/net/ipv4/conf/wlp4s0/drop_unicast_in_l2_multicast: Read-only file system
1684247813.364145: nl80211: Failed to set IPv4 unicast in multicast filter

I did some tests and the current issue is only happening with this specific network (which itself is an extension of an eduroam network) and eduroam networks. The username + password are correct, and the network configuration (including security, authentication, and CA certificate), is also as recommended by eduroam.

The initial behaviour reported in my first post is no longer observable to every network (it seemed to fix itself when I connected the laptop to wired connection and ran some system upgrades) but only with Eduroam networks at the moment.

Good that:

  1. You did use /var/log/wpa_supplicant.log
  2. most problems “did fix itself”

Eduroam…

1 Like

Most likely it was user error and I did something that resulted in that unwanted behaviour, until zypper saved me there.
As for the Eduroam specific problem, thank you for the directions. I will have a look into that !