NetworkManager not working and wifi going rouge.

Slackwarefanboy · 05-03-2019, 01:56 PM

Until recently I was able to use my network card as prescribed but recently network manager has all but gone haywire on me. I have 3 connections opitions for my network now: "4BB800, 4BB800 again and 4BB8000 1", I KNOW the cards works because it connects at first now to the last one but disconnects for some reason seconds after connecting. WHAT IS GOING ON? I can provide some relevant information. I am running Slackware 14.2, I have a wireless external adapter, the TP link TL-WN722N. I know the firmware is working and the driver MUST BE INSTALLED Given the fact that I can ping google but as usual seconds after I do it, the connection is lost. I Know this must have something to do with the NetworkManager's handling of things but I am still kind of new to linux. When I run:

iwconfig:

Code:

bash-4.3# iwconfig
lo        no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:"4BB800"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:83:C7:4B:B8:08   
          Bit Rate:72.2 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-****-****-****-****-****-****   Security mode:open
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

ifconfig:

Code:

bash-4.3# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 40:8d:5c:cb:31:b4  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 6479  bytes 462903 (452.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6479  bytes 462903 (452.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 50:3e:aa:bb:6f:10  txqueuelen 1000  (Ethernet)
        RX packets 630  bytes 10552805 (10.0 MiB)
        RX errors 0  dropped 837  overruns 0  frame 0
        TX packets 547  bytes 1187314 (1.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

IDK what other codes I could run to try and fix this. I am only sending this to you via the short time frame I have AFTER reconnecting to the third iteration made of my network by networkmanager.
I recently disconnected my whole pc and had to bring it to the living room to do some things with a direct Ethernet connection, brought it back to my room and reconnected it.

Slackwarefanboy · 05-03-2019, 02:41 PM

Literally it will connect and then seconds later MAKE SURE to disconnect.

ferrari · 05-03-2019, 03:47 PM

Watch the NetworkManager logging in a separate terminal window during the connection process and up until the wifi link fails. That might help with pinpointing the underlying issue. Assuming logging is to /var/log/messages, do

Code:

tail -f /var/log/messages |grep -i networkmanager

Report back with the output.

phalange · 05-03-2019, 04:15 PM

Quote:

Originally Posted by Slackwarefanboy

it connects at first now to the last one but disconnects for some reason seconds after connecting.

I've bumped into this with some routers. From my notes:

Network Manager connect/disconnect infinite loop
EDIT /etc/NetworkManager/conf.d/00-dhcp-client.conf
change from dhcpcd to dhclient

See if this helps your issue.

linus72 · 05-03-2019, 04:17 PM

It's doing the same connect/disconnect in my installs too so I have to use wicd.

bassmadrigal · 05-03-2019, 04:37 PM

I suggest the same as phalange. Some routers just don't like dhcpcd (and others don't like dhclient). The file they mention is well documented. You just comment out the dhcpcd line and uncomment the dhclient line and then possibly restart Network Manager (it might work without restarting it -- just try connecting to another network).

SCerovec · 05-04-2019, 06:05 AM

I've resorted to wpa_supplicant (has a nice gui too, aptly named wpa_gui i autostart thru gksu)

I switch to network manager for wwan (gsm/gprs) and some one-off wlan and back to wpa_supplicant for usual wifi on home router or tether from phone

HTH

Slackwarefanboy · 05-05-2019, 05:33 PM

Quote:

Originally Posted by phalange

I've bumped into this with some routers. From my notes:

Network Manager connect/disconnect infinite loop
EDIT /etc/NetworkManager/conf.d/00-dhcp-client.conf
change from dhcpcd to dhclient

See if this helps your issue.

Interesting, it sucks because I get wifi for free because my housemate pays for it and doesn't know the immense value it has to me with out charging, plus the stupid cable companies force you to use certain modems and routers, thank you for the information.

Richard Cranium · 05-05-2019, 07:01 PM

Quote:

Originally Posted by Slackwarefanboy

Interesting, it sucks because I get wifi for free because my housemate pays for it and doesn't know the immense value it has to me with out charging, plus the stupid cable companies force you to use certain modems and routers, thank you for the information.

Your housemate must be a saint.