Wifi connection stopping periodically requiring reset

Questions about WIFI networks and devices
Forum rules
Before you post please read how to get help
dhdurgee
Level 4
Level 4
Posts: 273
Joined: Thu Jul 02, 2009 7:56 pm

Wifi connection stopping periodically requiring reset

Postby dhdurgee » Tue Nov 21, 2017 5:07 pm

I recently upgraded to 18.2 x64 cinnamon and am now encountering a problem with my office WiFi connection stopping periodically requiring me to turn off the receiver and then turn it back on to resume operation. I thought to check the logs the last time I encountered this problem and found this in syslog:

Code: Select all

Nov 21 12:25:06 Z560 avahi-daemon[916]: Withdrawing address record for 192.168.230.233 on wlp5s0.
Nov 21 12:25:06 Z560 avahi-daemon[916]: Leaving mDNS multicast group on interface wlp5s0.IPv4 with address 192.168.230.233.
Nov 21 12:25:06 Z560 avahi-daemon[916]: Interface wlp5s0.IPv4 no longer relevant for mDNS.
Nov 21 12:25:08 Z560 ntpd[1469]: Deleting interface #18 wlp5s0, 192.168.230.233#123, interface stats: received=425, sent=433, dropped=0, active_time=86402 secs
Nov 21 12:25:08 Z560 ntpd[1469]: 208.88.126.235 local addr 192.168.230.233 -> <null>
Nov 21 12:25:08 Z560 ntpd[1469]: 171.66.97.126 local addr 192.168.230.233 -> <null>
Nov 21 12:25:08 Z560 ntpd[1469]: 204.9.54.119 local addr 192.168.230.233 -> <null>
Nov 21 12:25:08 Z560 ntpd[1469]: 91.189.91.157 local addr 192.168.230.233 -> <null>
Nov 21 12:25:08 Z560 ntpd[1469]: 91.189.89.199 local addr 192.168.230.233 -> <null>
Nov 21 12:28:08 Z560 avahi-daemon[916]: Interface wlp5s0.IPv6 no longer relevant for mDNS.
Nov 21 12:28:08 Z560 avahi-daemon[916]: Leaving mDNS multicast group on interface wlp5s0.IPv6 with address fe80::9d28:bee9:e967:a92d.
Nov 21 12:28:08 Z560 avahi-daemon[916]: Withdrawing address record for fe80::9d28:bee9:e967:a92d on wlp5s0.
Nov 21 12:28:08 Z560 NetworkManager[990]: <info>  [1511285288.3915] manager: WiFi hardware radio set disabled
Nov 21 12:28:08 Z560 NetworkManager[990]: <info>  [1511285288.3916] device (wlp5s0): state change: activated -> unavailable (reason 'none') [100 20 0]
Nov 21 12:28:08 Z560 systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 21 12:28:08 Z560 NetworkManager[990]: <info>  [1511285288.4241] dhcp4 (wlp5s0): canceled DHCP transaction, DHCP client pid 31792
Nov 21 12:28:08 Z560 NetworkManager[990]: <info>  [1511285288.4241] dhcp4 (wlp5s0): state changed bound -> done
Nov 21 12:28:08 Z560 wpa_supplicant[1224]: rfkill: WLAN soft blocked
Nov 21 12:28:08 Z560 wpa_supplicant[1224]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=00:26:f2:f8:da:ac reason=3 locally_generated=1
Nov 21 12:28:08 Z560 wpa_supplicant[1224]: rfkill: WLAN soft blocked
Nov 21 12:28:08 Z560 dnsmasq[1290]: setting upstream servers from DBus
Nov 21 12:28:08 Z560 NetworkManager[990]: <info>  [1511285288.6319] dns-mgr: Writing DNS information to /sbin/resolvconf
Nov 21 12:28:08 Z560 wpa_supplicant[1224]: rfkill: WLAN soft blocked
Nov 21 12:28:08 Z560 systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 21 12:28:08 Z560 NetworkManager[990]: <info>  [1511285288.7766] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 21 12:28:08 Z560 NetworkManager[990]: <info>  [1511285288.7769] manager: NetworkManager state is now DISCONNECTED
Nov 21 12:28:08 Z560 NetworkManager[990]: <info>  [1511285288.8359] audit: op="radio-control" arg="wireless-enabled:0" pid=2055 uid=1000 result="success"
Nov 21 12:28:08 Z560 NetworkManager[990]: <info>  [1511285288.8416] manager: WiFi now disabled by radio killswitch
Nov 21 12:28:08 Z560 wpa_supplicant[1224]: nl80211: deinit ifname=wlp5s0 disabled_11b_rates=0
Nov 21 12:28:08 Z560 dbus[944]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov 21 12:28:09 Z560 systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 21 12:28:09 Z560 dbus[944]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 21 12:28:09 Z560 systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 21 12:28:09 Z560 nm-dispatcher: req:1 'down' [wlp5s0]: new request (1 scripts)
Nov 21 12:28:09 Z560 nm-dispatcher: req:1 'down' [wlp5s0]: start running ordered scripts...
Nov 21 12:28:10 Z560 ntpd[1469]: Deleting interface #19 wlp5s0, fe80::9d28:bee9:e967:a92d%3#123, interface stats: received=0, sent=0, dropped=0, active_time=86584 secs
Nov 21 12:28:42 Z560 NetworkManager[990]: <info>  [1511285322.1896] manager: WiFi hardware radio set enabled
Nov 21 12:28:42 Z560 NetworkManager[990]: <info>  [1511285322.1912] audit: op="radio-control" arg="wireless-enabled:1" pid=2055 uid=1000 result="success"
Nov 21 12:28:42 Z560 systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 21 12:28:42 Z560 wpa_supplicant[1224]: rfkill: WLAN hard blocked
Nov 21 12:28:42 Z560 systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 21 12:28:42 Z560 wpa_supplicant[1224]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Nov 21 12:28:42 Z560 wpa_supplicant[1224]: dbus: Failed to construct signal
Nov 21 12:28:42 Z560 NetworkManager[990]: <info>  [1511285322.3466] device (wlp5s0): supplicant interface state: starting -> ready
Nov 21 12:28:42 Z560 NetworkManager[990]: <info>  [1511285322.3468] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Nov 21 12:28:42 Z560 wpa_supplicant[1224]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Nov 21 12:28:42 Z560 kernel: [660478.640902] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Nov 21 12:28:42 Z560 wpa_supplicant[1224]: rfkill: WLAN unblocked
Nov 21 12:28:42 Z560 NetworkManager[990]: <info>  [1511285322.7601] manager: WiFi now enabled by radio killswitch
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.7647] policy: auto-activating connection 'Auto Babylon_3807'
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.7783] policy: auto-activating connection 'Auto Babylon_3807'
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.7795] device (wlp5s0): Activation: starting connection 'Auto Babylon_3807' (e1732c09-45cb-45e5-8935-0f12db612699)
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.7799] device (wlp5s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.7803] manager: NetworkManager state is now CONNECTING
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.7812] device (wlp5s0): state change: prepare -> config (reason 'none') [40 50 0]
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.7827] device (wlp5s0): Activation: (wifi) access point 'Auto Babylon_3807' has security, but secrets are required.
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.7831] device (wlp5s0): state change: config -> need-auth (reason 'none') [50 60 0]
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.8557] device (wlp5s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.8563] device (wlp5s0): state change: prepare -> config (reason 'none') [40 50 0]
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.8570] device (wlp5s0): Activation: (wifi) connection 'Auto Babylon_3807' has security, and secrets exist.  No new secrets needed.
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.8574] Config: added 'ssid' value 'Babylon_3807'
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.8577] Config: added 'scan_ssid' value '1'
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.8580] Config: added 'key_mgmt' value 'WPA-PSK'
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.8583] Config: added 'auth_alg' value 'OPEN'
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.8586] Config: added 'psk' value '<omitted>'
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.8797] sup-iface[0x12f49f0,wlp5s0]: config: set interface ap_scan to 1
Nov 21 12:28:45 Z560 wpa_supplicant[1224]: wlp5s0: Trying to associate with 00:26:f2:f8:da:ac (SSID='Babylon_3807' freq=2412 MHz)
Nov 21 12:28:45 Z560 NetworkManager[990]: <info>  [1511285325.9413] device (wlp5s0): supplicant interface state: ready -> associating
Nov 21 12:28:45 Z560 wpa_supplicant[1224]: wlp5s0: Associated with 00:26:f2:f8:da:ac
Nov 21 12:28:45 Z560 wpa_supplicant[1224]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 21 12:28:46 Z560 NetworkManager[990]: <info>  [1511285326.0130] device (wlp5s0): supplicant interface state: associating -> associated
Nov 21 12:28:46 Z560 NetworkManager[990]: <info>  [1511285326.0284] device (wlp5s0): supplicant interface state: associated -> 4-way handshake
Nov 21 12:28:46 Z560 wpa_supplicant[1224]: wlp5s0: WPA: Key negotiation completed with 00:26:f2:f8:da:ac [PTK=CCMP GTK=CCMP]
Nov 21 12:28:46 Z560 wpa_supplicant[1224]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to 00:26:f2:f8:da:ac completed [id=0 id_str=]
Nov 21 12:28:46 Z560 NetworkManager[990]: <info>  [1511285326.0864] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 21 12:28:46 Z560 NetworkManager[990]: <info>  [1511285326.0874] device (wlp5s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Babylon_3807'.
Nov 21 12:28:46 Z560 NetworkManager[990]: <info>  [1511285326.0876] device (wlp5s0): state change: config -> ip-config (reason 'none') [50 70 0]
Nov 21 12:28:46 Z560 NetworkManager[990]: <info>  [1511285326.0882] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds)
Nov 21 12:28:46 Z560 NetworkManager[990]: <info>  [1511285326.1333] dhcp4 (wlp5s0): dhclient started with pid 2966
Nov 21 12:28:46 Z560 dhclient[2966]: DHCPREQUEST of 192.168.230.233 on wlp5s0 to 255.255.255.255 port 67 (xid=0x3591e027)
Nov 21 12:28:47 Z560 avahi-daemon[916]: Joining mDNS multicast group on interface wlp5s0.IPv6 with address fe80::9d28:bee9:e967:a92d.
Nov 21 12:28:47 Z560 avahi-daemon[916]: New relevant interface wlp5s0.IPv6 for mDNS.
Nov 21 12:28:47 Z560 avahi-daemon[916]: Registering new address record for fe80::9d28:bee9:e967:a92d on wlp5s0.*.
Nov 21 12:28:47 Z560 dhclient[2966]: DHCPACK of 192.168.230.233 from 192.168.230.1
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4732]   address 192.168.230.233
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4732]   plen 24 (255.255.255.0)
Nov 21 12:28:47 Z560 dhclient[2966]: bound to 192.168.230.233 -- renewal in 37505 seconds.
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4733]   gateway 192.168.230.1
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4734]   server identifier 192.168.230.1
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4734]   lease time 86400
Nov 21 12:28:47 Z560 avahi-daemon[916]: Joining mDNS multicast group on interface wlp5s0.IPv4 with address 192.168.230.233.
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4734]   nameserver '192.168.230.1'
Nov 21 12:28:47 Z560 avahi-daemon[916]: New relevant interface wlp5s0.IPv4 for mDNS.
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4735] dhcp4 (wlp5s0): state changed unknown -> bound
Nov 21 12:28:47 Z560 avahi-daemon[916]: Registering new address record for 192.168.230.233 on wlp5s0.IPv4.
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4769] device (wlp5s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4787] device (wlp5s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4797] device (wlp5s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4800] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4826] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4828] policy: set 'Auto Babylon_3807' (wlp5s0) as default for IPv4 routing and DNS
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4830] dns-mgr: Writing DNS information to /sbin/resolvconf
Nov 21 12:28:47 Z560 dnsmasq[1290]: setting upstream servers from DBus
Nov 21 12:28:47 Z560 dnsmasq[1290]: using nameserver 192.168.230.1#53(via wlp5s0)
Nov 21 12:28:47 Z560 NetworkManager[990]: <info>  [1511285327.4961] device (wlp5s0): Activation: successful, device activated.
Nov 21 12:28:47 Z560 dbus[944]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov 21 12:28:47 Z560 systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 21 12:28:47 Z560 dbus[944]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 21 12:28:47 Z560 systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 21 12:28:47 Z560 nm-dispatcher: req:1 'up' [wlp5s0]: new request (1 scripts)
Nov 21 12:28:47 Z560 nm-dispatcher: req:1 'up' [wlp5s0]: start running ordered scripts...


As syslog shows, avahi-daemon, whatever that is, appears to have done something at 12:25:06 that halted operation of my WiFi connection. At 12:28:08 I turned off the WiFi from the panel and then turned it back on at 12:28:42 which restarted things and returned me to normal operation.

What is avahi-daemon and why did it shut me down? Am I mistaken about this? Is there another reason my WiFi is stopping and requiring a power cycle to resume operation?

I will be happy to dig further into this for someone who can help me diagnose and correct this problem.

Dave
Last edited by JeremyB on Tue Dec 12, 2017 2:44 pm, edited 1 time in total.
Reason: added code tags

User avatar
Spearmint2
Level 14
Level 14
Posts: 5307
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Wifi connection stopping periodically requiring reset

Postby Spearmint2 » Tue Nov 21, 2017 6:42 pm

Go into the networking settings and disable IPv6 and see if things improve.
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

dhdurgee
Level 4
Level 4
Posts: 273
Joined: Thu Jul 02, 2009 7:56 pm

Re: Wifi connection stopping periodically requiring reset

Postby dhdurgee » Tue Nov 21, 2017 6:53 pm

Spearmint2 wrote:Go into the networking settings and disable IPv6 and see if things improve.


Just did so. Will see if this helps.

Dave

dhdurgee
Level 4
Level 4
Posts: 273
Joined: Thu Jul 02, 2009 7:56 pm

Re: Wifi connection stopping periodically requiring reset

Postby dhdurgee » Tue Dec 12, 2017 8:45 am

I regret to say that I am again encountering this problem. This morning I once again had to turn the WiFi off for a few seconds and back on to restart communications. The errors logged were similar to last time:

Code: Select all

Dec 12 07:00:15 Z560 wpa_supplicant[1237]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Dec 12 07:17:00 Z560 wpa_supplicant[1237]: message repeated 1012 times: [ wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1]
Dec 12 07:17:01 Z560 CRON[22374]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 12 07:17:01 Z560 wpa_supplicant[1237]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Dec 12 07:23:54 Z560 wpa_supplicant[1237]: message repeated 416 times: [ wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1]
Dec 12 07:23:55 Z560 wpa_supplicant[1237]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Dec 12 07:24:00 Z560 wpa_supplicant[1237]: message repeated 5 times: [ wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1]
Dec 12 07:24:01 Z560 cinnamon-screensaver-pam-helper: pam_ecryptfs: seteuid error
Dec 12 07:24:01 Z560 wpa_supplicant[1237]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Dec 12 07:25:01 Z560 wpa_supplicant[1237]: message repeated 60 times: [ wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1]
Dec 12 07:25:02 Z560 wpa_supplicant[1237]: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Dec 12 07:26:03 Z560 wpa_supplicant[1237]: message repeated 61 times: [ wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1]
Dec 12 07:26:03 Z560 wpa_supplicant[1237]: rfkill: WLAN soft blocked
Dec 12 07:26:03 Z560 wpa_supplicant[1237]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=00:26:f2:f8:da:ac reason=3 locally_generated=1
Dec 12 07:26:03 Z560 kernel: [162572.593102] ERROR @wl_notify_scan_status : wlp5s0 Scan_results error (-22)
Dec 12 07:26:03 Z560 NetworkManager[1011]: <info>  [1513081563.4876] manager: WiFi hardware radio set disabled


I disabled IPv6 in the settings as suggested last time. This may have helped, but the problem is still here. Is anyone else seeing this? What do the error messages from wpa_supplicant indicate? Do they give a clue how to stop this from occurring?

Dave

thx-1138
Level 3
Level 3
Posts: 114
Joined: Fri Mar 10, 2017 12:15 pm
Location: Athens, Greece

Re: Wifi connection stopping periodically requiring reset

Postby thx-1138 » Tue Dec 12, 2017 9:55 am

Dec 12 07:26:03 Z560 wpa_supplicant[1237]: rfkill: WLAN soft blocked

Try:

Code: Select all

rfkill list all
See what's blocked, then try "rfkill unblock wlan" (most likely...)

User avatar
Spearmint2
Level 14
Level 14
Posts: 5307
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Wifi connection stopping periodically requiring reset

Postby Spearmint2 » Tue Dec 12, 2017 1:02 pm

Has it occurred to you the inbuilt wifi device is likely in process of dying? Try a USB wifi device and see if the problem continues. If not, you know where the problem is.I use this one. It works in Linux and Windows both. Great range too.
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

dhdurgee
Level 4
Level 4
Posts: 273
Joined: Thu Jul 02, 2009 7:56 pm

Re: Wifi connection stopping periodically requiring reset

Postby dhdurgee » Tue Dec 12, 2017 4:58 pm

Spearmint2 wrote:Has it occurred to you the inbuilt wifi device is likely in process of dying? Try a USB wifi device and see if the problem continues. If not, you know where the problem is.I use this one. It works in Linux and Windows both. Great range too.


Had not really considered a hardware failure, but I will cede your point. Should it die I would definitely consider such a solution for remote use. For office use I can use the LAN port instead.

Dave


Return to “Wireless”