Wifi randomly disconnects on tumbleweed

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 turned power management off. i am not sure what else i should try.

You could start with showing at least some information, like logs when it happened. Something like (as root)

journalctl --no-pager --full --since '1 day ago'`

and upload to https://paste.opensuse.org.

Oops , wrong thread - sorry

here is the log pasted: openSUSE Paste

the first line about hubble is the software i am running. That is the last log line of that software which shutdown.

I wonder what that script is doing there.
It’s not there on my system, in fact there are no scripts in /etc/NetworkManager/dispatcher.d/ directory.

For NTP time synchronization, I use chrony package and its systemd service chronyd.service.

It covers 20 minutes and there is nothing about any wifi problem. Provide output of

journalctl -b --no-pager --full

I ended up reinstalling tumbleweed and I no longer have the wifi disconnecting issue.

Though I still keep getting the server not being accessible from my local machine after some time. It also seems very random.

I turned off suspend with this command sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target

but it still becomes inactive. i even logged into the server physically this morning after realizing i am no longer able to ping the server, but my laptop still cannot ping my server until i restarted it (presumably restarting network would also have worked - but i wanted to check something in the bios - nothing there either related to power management)

also to note the services i had running on the server are all good. they continue to access the internet. it is just my laptop not able to access the server through a ping or a ssh.

if everytime i have to access my server, i have to physically do somethign on the server, its very incovenient. i need to find a solution for this.

Could you try booting with the kernel command line option acpi=off and disable tlp.service if it’s installed/enabled.

This makes me think the firewall is involved somehow, what sort of services are running on the server?

What “suspend” are you talking about? Do you know what these units do?

Does your laptop has connectivity to other hosts on your network, to your router or to the Internet when it cannot ping the server?

services i am running are couple of decentralized nodes as part of a couple of projects.

when i login physically on the server, i am able to access the internet.

will boot the kernel and try later today.

thanks.

What “suspend” are you talking about? Do you know what these units do?

I was thinking my server is going into sleep/suspend/hibernate mode and wanted to make sure it did not. Researchign a bit, was suggested to mask these.

Does your laptop has connectivity to other hosts on your network, to your router or to the Internet when it cannot ping the server?

I could access the internet. Did not try other hosts.

Are your laptop and server in the same LAN? Show the output of ip a from both systems.

Yes, they are both on same wifi/subnet/gateway.

on opensuse:
ip addr show
inet /24

ip route show
default via

on my mac laptop> going into settings → wifi has the same ip address and router ip as above.

oh no, the grey wifi icon with question mark is back today morning.

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

Does anyone know why that happens randomly?

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.

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