Unstable Network Manager

Kernels & Hardware, configuring network, installing services

Unstable Network Manager

Postby Speedcuber » 2017-08-05 16:17

I'm running Debian Stretch, my problem is that the internet stop working after 1 or 2 minutes of connection, even if the network manager icon shows that it's connected. To solve it I enable then disable Airplane mode, it works for just for 1 to 5 minutes, and sometimes it asks me to enter the WPA2 key.

Some information about the system:

Code: Select all
$ uname -a
Linux debian 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 GNU/Linux


Code: Select all
$ lspci | grep 802
02:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01)


Code: Select all
# cat  /var/log/syslog
g  5 16:56:38 debian systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug  5 16:56:38 debian systemd[1]: Started Load/Save RF Kill Switch Status.
Aug  5 16:56:38 debian dbus[473]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug  5 16:56:38 debian systemd[1]: Started Network Manager Script Dispatcher Service.
Aug  5 16:56:38 debian nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
Aug  5 16:56:38 debian nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Aug  5 16:56:38 debian nm-dispatcher: req:2 'down' [wlp2s0]: new request (1 scripts)
Aug  5 16:56:38 debian nm-dispatcher: req:2 'down' [wlp2s0]: start running ordered scripts...
Aug  5 16:56:38 debian wpa_supplicant[541]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
Aug  5 16:56:40 debian systemd-timesyncd[448]: Timed out waiting for reply from 196.200.131.160:123 (0.debian.pool.ntp.org).
Aug  5 16:57:39 debian systemd[1]: Starting Load/Save RF Kill Switch Status...
Aug  5 16:57:39 debian NetworkManager[477]: <info>  [1501948659.1521] manager: WiFi now enabled by radio killswitch
Aug  5 16:57:39 debian systemd[1]: Started Load/Save RF Kill Switch Status.
Aug  5 16:57:39 debian NetworkManager[477]: <info>  [1501948659.1960] sup-iface[0x7fe48c004830,wlp2s0]: supports 1 scan SSIDs
Aug  5 16:57:39 debian NetworkManager[477]: <info>  [1501948659.1967] device (wlp2s0): supplicant interface state: starting -> ready
Aug  5 16:57:39 debian NetworkManager[477]: <info>  [1501948659.1968] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1407] device (wlp2s0): supplicant interface state: ready -> inactive
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1443] policy: auto-activating connection 'Forthnet-309F50'
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1459] device (wlp2s0): Activation: starting connection 'Forthnet-309F50' (35490d26-7a7e-45e5-a345-772464698f40)
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1462] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1463] manager: NetworkManager state is now CONNECTING
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1473] device (wlp2s0): set-hw-addr: reset MAC address to 44:1C:A8:97:1F:85 (preserve)
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1486] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1489] device (wlp2s0): Activation: (wifi) access point 'Forthnet-309F50' has security, but secrets are required.
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1489] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0]
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1928] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1932] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1951] device (wlp2s0): Activation: (wifi) connection 'Forthnet-309F50' has security, and secrets exist.  No new secrets needed.
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1951] Config: added 'ssid' value 'Forthnet-309F50'
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1951] Config: added 'scan_ssid' value '1'
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1952] Config: added 'bssid' value '18:17:25:30:9F:50'
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1952] Config: added 'key_mgmt' value 'WPA-PSK'
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.1952] Config: added 'psk' value '<hidden>'
Aug  5 16:57:40 debian wpa_supplicant[541]: wlp2s0: Trying to associate with 18:17:25:30:9f:50 (SSID='Forthnet-309F50' freq=2462 MHz)
Aug  5 16:57:40 debian NetworkManager[477]: <info>  [1501948660.2223] device (wlp2s0): supplicant interface state: inactive -> associating
Aug  5 16:57:40 debian kernel: [  175.636396] ERROR @wl_notify_scan_status :
Aug  5 16:57:40 debian kernel: [  175.636402] wlp2s0 Scan_results error (-22)
Aug  5 16:57:49 debian wpa_supplicant[541]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=18:17:25:30:9f:50 reason=3 locally_generated=1
Aug  5 16:57:49 debian wpa_supplicant[541]: rfkill: WLAN soft blocked
Aug  5 16:57:49 debian systemd[1]: Starting Load/Save RF Kill Switch Status...
Aug  5 16:57:49 debian NetworkManager[477]: <info>  [1501948669.3727] manager: WiFi now disabled by radio killswitch
Aug  5 16:57:49 debian NetworkManager[477]: <info>  [1501948669.3728] device (wlp2s0): state change: config -> unavailable (reason 'none') [50 20 0]
Aug  5 16:57:49 debian NetworkManager[477]: <info>  [1501948669.3739] device (wlp2s0): set-hw-addr: set MAC address to 72:F1:8D:9E:D6:CB (scanning)
Aug  5 16:57:49 debian NetworkManager[477]: <info>  [1501948669.3749] manager: NetworkManager state is now DISCONNECTED
Aug  5 16:57:49 debian systemd[1]: Started Load/Save RF Kill Switch Status.
Aug  5 16:57:49 debian wpa_supplicant[541]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
Aug  5 16:57:50 debian NetworkManager[477]: <info>  [1501948670.2731] manager: WiFi now enabled by radio killswitch
Aug  5 16:57:50 debian NetworkManager[477]: <info>  [1501948670.3277] sup-iface[0x55f2d88aa4a0,wlp2s0]: supports 1 scan SSIDs
Aug  5 16:57:50 debian NetworkManager[477]: <info>  [1501948670.3284] device (wlp2s0): supplicant interface state: starting -> ready
Aug  5 16:57:50 debian NetworkManager[477]: <info>  [1501948670.3285] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2197] device (wlp2s0): supplicant interface state: ready -> inactive
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2268] policy: auto-activating connection 'Forthnet-309F50'
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2284] device (wlp2s0): Activation: starting connection 'Forthnet-309F50' (35490d26-7a7e-45e5-a345-772464698f40)
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2287] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2288] manager: NetworkManager state is now CONNECTING
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2297] device (wlp2s0): set-hw-addr: reset MAC address to 44:1C:A8:97:1F:85 (preserve)
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2616] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2619] device (wlp2s0): Activation: (wifi) access point 'Forthnet-309F50' has security, but secrets are required.
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2620] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0]
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2686] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2696] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2703] device (wlp2s0): Activation: (wifi) connection 'Forthnet-309F50' has security, and secrets exist.  No new secrets needed.
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2707] Config: added 'ssid' value 'Forthnet-309F50'
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2711] Config: added 'scan_ssid' value '1'
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2714] Config: added 'bssid' value '18:17:25:30:9F:50'
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2718] Config: added 'key_mgmt' value 'WPA-PSK'
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.2721] Config: added 'psk' value '<hidden>'
Aug  5 16:57:51 debian wpa_supplicant[541]: wlp2s0: Trying to associate with 18:17:25:30:9f:50 (SSID='Forthnet-309F50' freq=2462 MHz)
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.3234] device (wlp2s0): supplicant interface state: inactive -> associating
Aug  5 16:57:51 debian kernel: [  186.735142] ERROR @wl_notify_scan_status :
Aug  5 16:57:51 debian kernel: [  186.735145] wlp2s0 Scan_results error (-22)
Aug  5 16:57:51 debian wpa_supplicant[541]: wlp2s0: CTRL-EVENT-ASSOC-REJECT bssid=18:17:25:30:9f:50 status_code=16
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.3778] device (wlp2s0): supplicant interface state: associating -> disconnected
Aug  5 16:57:51 debian NetworkManager[477]: <info>  [1501948671.4785] device (wlp2s0): supplicant interface state: disconnected -> scanning
Aug  5 16:57:52 debian wpa_supplicant[541]: wlp2s0: Trying to associate with 18:17:25:30:9f:50 (SSID='Forthnet-309F50' freq=2462 MHz)
Aug  5 16:57:52 debian NetworkManager[477]: <info>  [1501948672.3630] device (wlp2s0): supplicant interface state: scanning -> associating
Aug  5 16:57:52 debian wpa_supplicant[541]: wlp2s0: CTRL-EVENT-ASSOC-REJECT bssid=18:17:25:30:9f:50 status_code=16
Aug  5 16:57:52 debian NetworkManager[477]: <info>  [1501948672.4139] device (wlp2s0): supplicant interface state: associating -> disconnected
Aug  5 16:57:52 debian NetworkManager[477]: <info>  [1501948672.9145] device (wlp2s0): supplicant interface state: disconnected -> scanning
Aug  5 16:57:53 debian wpa_supplicant[541]: wlp2s0: Trying to associate with 18:17:25:30:9f:50 (SSID='Forthnet-309F50' freq=2462 MHz)
Aug  5 16:57:53 debian NetworkManager[477]: <info>  [1501948673.8006] device (wlp2s0): supplicant interface state: scanning -> associating
Aug  5 16:57:53 debian wpa_supplicant[541]: wlp2s0: Associated with 18:17:25:30:9f:50
Aug  5 16:57:53 debian NetworkManager[477]: <info>  [1501948673.9258] device (wlp2s0): supplicant interface state: associating -> 4-way handshake
Aug  5 16:57:53 debian wpa_supplicant[541]: wlp2s0: WPA: Key negotiation completed with 18:17:25:30:9f:50 [PTK=CCMP GTK=TKIP]
Aug  5 16:57:53 debian wpa_supplicant[541]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 18:17:25:30:9f:50 completed [id=0 id_str=]
Aug  5 16:57:53 debian NetworkManager[477]: <info>  [1501948673.9366] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Aug  5 16:57:53 debian NetworkManager[477]: <info>  [1501948673.9367] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Forthnet-309F50'.
Aug  5 16:57:53 debian NetworkManager[477]: <info>  [1501948673.9367] device (wlp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Aug  5 16:57:53 debian avahi-daemon[492]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.69.
Aug  5 16:57:53 debian avahi-daemon[492]: New relevant interface wlp2s0.IPv4 for mDNS.
Aug  5 16:57:53 debian avahi-daemon[492]: Registering new address record for 192.168.1.69 on wlp2s0.IPv4.
Aug  5 16:57:53 debian NetworkManager[477]: <info>  [1501948673.9449] device (wlp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Aug  5 16:57:53 debian NetworkManager[477]: <info>  [1501948673.9562] device (wlp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Aug  5 16:57:53 debian NetworkManager[477]: <info>  [1501948673.9566] device (wlp2s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Aug  5 16:57:53 debian NetworkManager[477]: <info>  [1501948673.9568] manager: NetworkManager state is now CONNECTED_LOCAL
Aug  5 16:57:53 debian dbus[473]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Aug  5 16:57:53 debian systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug  5 16:57:53 debian dbus[473]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug  5 16:57:53 debian systemd[1]: Started Network Manager Script Dispatcher Service.
Aug  5 16:57:53 debian nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
Aug  5 16:57:53 debian nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Aug  5 16:57:54 debian NetworkManager[477]: <info>  [1501948674.0212] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug  5 16:57:54 debian NetworkManager[477]: <info>  [1501948674.0213] policy: set 'Forthnet-309F50' (wlp2s0) as default for IPv4 routing and DNS
Aug  5 16:57:54 debian NetworkManager[477]: <info>  [1501948674.0217] device (wlp2s0): Activation: successful, device activated.
Aug  5 16:57:54 debian nm-dispatcher: req:2 'up' [wlp2s0]: new request (1 scripts)
Aug  5 16:57:54 debian nm-dispatcher: req:2 'up' [wlp2s0]: start running ordered scripts...
Aug  5 16:57:55 debian avahi-daemon[492]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::461c:a8ff:fe97:1f85.
Aug  5 16:57:55 debian avahi-daemon[492]: New relevant interface wlp2s0.IPv6 for mDNS.
Aug  5 16:57:55 debian avahi-daemon[492]: Registering new address record for fe80::461c:a8ff:fe97:1f85 on wlp2s0.*.
Speedcuber
 
Posts: 4
Joined: 2017-08-05 11:07

Re: Unstable Network Manager

Postby Bulkley » 2017-08-05 17:10

Network Manager is a beautiful piece of software when it's working and a royal pain when it's not. Usually, the problem is mis-configuration by the installer. As an easy test re-name Network Manager's user config in the ~/. files and start again. It should create a new user config and you should have to re-enter stuff.

Is this on a laptop or desktop?
Bulkley
 
Posts: 5281
Joined: 2006-02-11 18:35

Re: Unstable Network Manager

Postby Speedcuber » 2017-08-05 17:26

It's an HP Notebook 14-am003nk, can you explain more how can I create a new user configuration ?
Speedcuber
 
Posts: 4
Joined: 2017-08-05 11:07

Re: Unstable Network Manager

Postby Bulkley » 2017-08-05 17:52

Speedcuber wrote: . . . can you explain more how can I create a new user configuration ?


Shut off Network Manager, and rename your user configuration, whatever it's called. Then restart user Network Manager and it will create a new user configuration. I can't give you a detailed step by step because I don't use Network Manager, gave up on it years ago.

If you read the syslog you posted you will see that NM uses wpa_supplicant. It is wpa_supplicant that does the work; NM is merely a GUI with a bunch of scripts so that users can push buttons. Many users get fed up with NM and replace it with Wicd. Others configure use CLI to configure wpa_supplicant directly.
Bulkley
 
Posts: 5281
Joined: 2006-02-11 18:35

Re: Unstable Network Manager

Postby Speedcuber » 2017-08-05 19:03

I decided moving to Connman which I used before and had no issues for me, but I hope that someone post a good solution to this problem because I believe that many NM users have it.
Speedcuber
 
Posts: 4
Joined: 2017-08-05 11:07

Re: Unstable Network Manager

Postby Speedcuber » 2017-08-05 20:58

Update: I tried using wicd, and I had the same annoying problem, which make the wireless connection almost unusable.
Speedcuber
 
Posts: 4
Joined: 2017-08-05 11:07

Re: Unstable Network Manager

Postby dilberts_left_nut » 2017-08-05 21:02

Seems to e a common complaint with Broadcom gear.
Replacing it would help.
AdrianTM wrote:There's no hacker in my grandma...
User avatar
dilberts_left_nut
 
Posts: 4658
Joined: 2009-10-05 07:54
Location: enzed


Return to System configuration

Who is online

Users browsing this forum: No registered users and 6 guests

fashionable