WIFI drops connection if computer is idle for a long time

English Network/Internet
1

I do NOT use Network Manager. I used YAST to configure my WIFI. I could NOT see if there is a power saving setting to shut off anywhere for the wifi adapter AND iwconfig says Power Management is off. Fresh install.

**linux-nfxl:~ #** iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11  ESSID:"********"  //shows up as real SSID, but I changed it to ****** 
          Mode:Managed  Frequency:2.462 GHz  Access Point: D4:AB:82:66:88:31    
          Bit Rate=144.4 Mb/s   Tx-Power=20 dBm    
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=62/70  Signal level=-48 dBm   
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:1400   Missed beacon:0

lo        no wireless extensions.

I tried to reconfigure my wifi in Yast and restart the networking, but that didn’t work. I had to reboot to get it to work again.

I don’t know where else to look. Please help.

2

This may be the way your AP is configured perhaps. Anyway, you can observe the logging with

sudo journalctl -fu wicked

I tried to reconfigure my wifi in Yast and restart the networking, but that didn’t work. I had to reboot to get it to work again.

I don’t know where else to look. Please help.

Next time the connection drops try toggling the interface like this

sudo ifdown wlan0;sudo ifup wlan0
3

Thanks. I have used the ifup and ifdown commands before and I will remember to use them the next time the wifi drops the connection. As for the journalctl command, I copied and pasted it in a text document so that it will be available offline.

Thanks so much!!!

4

this also happening in tumbleweed 64bit when using wicked. however, with NetworkManager this doesn’t seem to happen

5

The wifi did NOT go down today. It may have been a one time thing. If it doesn’t occur again tomorrow, I will mark this thread as resolved.

6

If you’re not using Network Manager, the system is, possibly, using Wicked:

  • Please check the output of “ systemctl list-unit-files | grep -iE ‘network|wicked’
    ” – you’ll possibly see that, the Network Manager services are disabled and, the Wicked services are enabled … - If Wicked, then, with the user “root”:

“wicked ifstatus all”
“wicked ifcheck --missed --changed --persistent wlan0” (or, “all”)

I’ve no idea if, “wicked ethtool” functions correctly with WLAN hardware …