Wifi question mark icon randomly on tumbleweed (connected_global to connected_site state change)

English Network/Internet
1

my wifi randomly gets disabled. it turns into a grey icon with a question mark on it. when i go and disable and enable again, it connects. but same thing happens again after some time.

I narrowed down the grey wifi icon with question mark to NetworkManager state changing from CONNECTED_GLOBAL to CONNECTED_SITE.

I enable debug logs and found this before the state changes to connected_site

Mar 16 09:19:52 localhost.localdomain NetworkManager[1785]: <debug> [1710605992.7949] connectivity: (br-feaa938eb8db,IPv4,8021) skip connectivity check due to no global route configured
Mar 16 09:19:52 localhost.localdomain NetworkManager[1785]: <debug> [1710605992.7950] connectivity: (br-feaa938eb8db,IPv6,8022) start request to 'http://conncheck.opensuse.org' (try resolving 'conncheck.opensuse.org' using system resolver)
Mar 16 09:19:52 localhost.localdomain NetworkManager[1785]: <debug> [1710605992.7952] connectivity: (br-feaa938eb8db,IPv4,8021) check completed: LIMITED; no global route configured
Mar 16 09:19:59 localhost.localdomain NetworkManager[1785]: <debug> [1710605999.1536] connectivity: (wlp68s0,IPv4,8023) start request to 'http://conncheck.opensuse.org' (try resolving 'conncheck.opensuse.org' using system resolver)
Mar 16 09:20:22 localhost.localdomain NetworkManager[1785]: <debug> [1710606022.8201] connectivity: (br-feaa938eb8db,IPv6,8022) failure to resolve name: Socket I/O timed out
Mar 16 09:20:22 localhost.localdomain NetworkManager[1785]: <debug> [1710606022.8202] connectivity: (br-feaa938eb8db,IPv6,8022) check completed: LIMITED; resolve-error
Mar 16 09:20:29 localhost.localdomain NetworkManager[1785]: <debug> [1710606029.1610] connectivity: (wlp68s0,IPv4,8023) failure to resolve name: Socket I/O timed out
Mar 16 09:20:29 localhost.localdomain NetworkManager[1785]: <debug> [1710606029.1611] connectivity: (wlp68s0,IPv4,8023) check completed: LIMITED; resolve-error
Mar 16 09:20:29 localhost.localdomain NetworkManager[1785]: <debug> [1710606029.1611] device[bd0f3abdae846b26] (wlp68s0): connectivity state changed from FULL to LIMITED
Mar 16 09:20:29 localhost.localdomain NetworkManager[1785]: <debug> [1710606029.1612] manager: connectivity checking indicates LIMITED
Mar 16 09:20:29 localhost.localdomain NetworkManager[1785]: <info>  [1710606029.1613] manager: NetworkManager state is now CONNECTED_SITE

Appreciate any help on understanding what may be going on.

2

Whatever happened, it happened before this line. Of course NetworkManager cannot verify connectivity to the Internet if routes are missing.

3

@arvidjaar how does one configure a global route?

This br-… device is a bridged interface as i run docker for one of my application.

the physical network interface is wlp68s0.

i can see that on that interface ipv6 is failing. i dont think i have ipv6 enabled on my router. how do i disable ipv6 connection checking on opensuse? is that being unnecessarily checked and subsequently resulting in these errors?

4

I am not sure I understand the question. Usually it is done by your network management application (NetworkManager in your case) according to its configuration. If you insist, you can define them manually using ip route. But again, missing route is most likely noth the root cause but just the consequence of some other problems with interface(s). As long as you do not provide logs covering this, it is impossible to guess what happens.

Disable IPv6 in your NetworkManager connection definition.

5

The servers I run spit out so much logs that, i am not sure what to specifically share. The one i shared above is just the NetworkManager.Service logs. Is there anything specific that I could filter it down to and share? Thanks for your help.

One thing I did is changed my Router. I was using an old one from 2016/17. It is due for an upgrade. Since I upgraded it (~4 hours) - didn’t lose the wifi yet.

So going to monitor that.

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.