[SOLVED] NetworkManager issues

Kernels & Hardware, configuring network, installing services

[SOLVED] NetworkManager issues

Postby Mike » 2018-10-07 20:37

I'll start by saying that this isn't really something that needs to be solved. Its more that I'm interested in any feedback of where it may have been going wrong.

Yesterday I was having some issues with NetworkManager in Gnome 3.30. What was happening is that if I used to NetworkManager to configure the connection I was getting errors like the example below. Even though it is stating the the ssid was not found it is correct. So as an attempt to eliminate testing as a problem, I quickly installed stable into a separate partition (separate /boot, same /home) which resulted in the same issue. In both cases the firmware was installed.

Code: Select all
Oct  6 14:52:49 debian NetworkManager[571]: <info>  [1538862769.1114] device (wlx60a44cec22f5): supplicant interface state: authenticating -> disconnected
Oct  6 14:52:49 debian NetworkManager[571]: <info>  [1538862769.6119] device (wlx60a44cec22f5): supplicant interface state: disconnected -> scanning
Oct  6 14:52:52 debian NetworkManager[571]: <warn>  [1538862772.4955] device (wlx60a44cec22f5): Activation: (wifi) association took too long, failing activation
Oct  6 14:52:52 debian NetworkManager[571]: <info>  [1538862772.4955] device (wlx60a44cec22f5): state change: config -> failed (reason 'ssid-not-found') [50 120 53]
Oct  6 14:52:52 debian NetworkManager[571]: <warn>  [1538862772.4959] device (wlx60a44cec22f5): Activation: failed for connection 'TELUS2084-5G'
Oct  6 14:52:52 debian NetworkManager[571]: <info>  [1538862772.5278] device (wlx60a44cec22f5): supplicant interface state: scanning -> disconnected
Oct  6 14:52:52 debian NetworkManager[571]: <info>  [1538862772.5368] device (wlx60a44cec22f5): state change: failed -> disconnected (reason 'none') [120 30 0]
Oct  6 14:52:52 debian kernel: [   84.044513] IPv6: ADDRCONF(NETDEV_UP): wlx60a44cec22f5: link is not ready


Where is gets odd is that if I configure the interface manually in /etc/interfaces everything works beautify. So I have removed NetworkManager since I don't need it anymore and I think it will stay that way now since my unmanaged connection seems to be working just fine. I would however be interested if anyone else has run into this issue. I would be interested in why NetworkManager seemed to be misbehaving.

I have since configured stable with a similar setup to what I was using in Testing + firefox from Sid. I would appear that for my use I don't really need to be running testing and getting piles of updates. I may just stay on stretch now and enjoy the calmer update frequency. Coming back to debian from Fedora I went to testing initially but Stable + some selected backports seems to be working just fine for now. That and I don't really want to mess with something thats working right now. :)
Last edited by Mike on 2018-10-08 23:47, edited 1 time in total.
Mike
 
Posts: 57
Joined: 2005-11-16 19:12
Location: Sunshine Coast, BC

Re: NetworkManager issues

Postby bw123 » 2018-10-07 22:10

There are some really strange issues with networkmanager. I decided to use it on my netbook awhile back and did some research. The issues are pretty well covered on it's bug page, https://bugs.debian.org/network-manager

From what I have read, some people believe these issues are driver related, affecting different devices in different ways. Others say wpasupplicant is the cause. Then there are those that blam the persistent naming features introduced with systemd/udev. Many users find relief by disabling or tweaking the random MAC features in networkmanager.

It's your call, I think it would be great if it got pinned down and improved. I have it very working very reliable on my old b43 wifi but it took a lot of tweaking and config trial and error. If you have the time, dig deeper and file a bug report with what you find out? Might help someone someday...
User avatar
bw123
 
Posts: 3400
Joined: 2011-05-09 06:02
Location: TN_USA

Re: NetworkManager issues

Postby Bulkley » 2018-10-07 22:18

NetworkManager is just a GUI; wpa-supplicant does the work. If you have a desktop that stays in one place and only uses one connection then a /etc/network/interfaces setup is all you need as you found out. Users seem to like NetworkManager for laptops that move around a lot. Frankly NetworkManager is finicky. Some users like Wicd; I prefer wpagui for a mobile machine.
Bulkley
 
Posts: 5630
Joined: 2006-02-11 18:35

Re: NetworkManager issues

Postby Mike » 2018-10-07 22:29

bw123 wrote:There are some really strange issues with networkmanager. I decided to use it on my netbook awhile back and did some research. The issues are pretty well covered on it's bug page, https://bugs.debian.org/network-manager


Thanks for the link, I'll have a browse through those. I'm sure I'll get back to investigating this but for the time being I'm going to take a bit of a break from digging around wireless configurations and doing the trial and error thing. If I do find anything that points to a cause I'll definitely be reporting a bug, or adding to an existing on depending on if I find one thats an exact match.

I may try and borrow another wireless adapter from someone that is not Asus/Realtek based. Switching to a different driver may at least eliminate it being related to a particular driver.

However tonight is Thanksgiving dinner for me. :)
Mike
 
Posts: 57
Joined: 2005-11-16 19:12
Location: Sunshine Coast, BC

Re: NetworkManager issues

Postby L_V » 2018-10-08 07:26

You should take care at the date of each bug...
First one: 2007: network-manager doesn't ignore aliased interfaces in /e/n/i

I wonder if some troubles are not caused by mixing differrent network system configurations.
Starting by having a look on these status might help:
Code: Select all
systemctl status {systemd-networkd,systemd-resolved,networking,NetworkManager,systemd-hostnamed,openvpn} |egrep -v 'man:|http'

@Mike
You have disabled NetworkManager.
Could you try to totally purge it and reinstall it ?

+ don't mix Stretch + Testing + SID for this kind of tests...... Only pure Stretch to see.
L_V
 
Posts: 799
Joined: 2007-03-19 09:04

Re: NetworkManager issues

Postby Mike » 2018-10-08 21:31

I think I am liking the system without NetworkManager, it is looking like its probably more trouble than its worth for a system that is always connecting to the same network. However since it would be good to know what the cause is here are the results of another attempt. :) Worth noting is that NetworkManager was working in Fedora before I moved back to debian so I don't think its any issue with the adapter itself.

L_V wrote:I wonder if some troubles are not caused by mixing differrent network system configurations.
Starting by having a look on these status might help:
Code: Select all
systemctl status {systemd-networkd,systemd-resolved,networking,NetworkManager,systemd-hostnamed,openvpn} |egrep -v 'man:|http'



Here is the result of that query.

Code: Select all
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-resolved.service.d
           └─resolvconf.conf
   Active: inactive (dead)

● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: active (exited) since Mon 2018-10-08 14:50:29 PDT; 5min ago
  Process: 577 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
  Process: 574 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=1/FAILURE)
 Main PID: 577 (code=exited, status=0/SUCCESS)

● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2018-10-08 14:50:31 PDT; 5min ago
 Main PID: 601 (NetworkManager)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
           └─601 /usr/sbin/NetworkManager --no-daemon

● systemd-hostnamed.service - Hostname Service
   Loaded: loaded (/lib/systemd/system/systemd-hostnamed.service; static; vendor preset: enabled)
   Active: inactive (dead)


L_V wrote:@Mike
You have disabled NetworkManager.
Could you try to totally purge it and reinstall it ?


Did this yesterday with no luck, and just tried it again. The result is the same errors.

L_V wrote:+ don't mix Stretch + Testing + SID for this kind of tests...... Only pure Stretch to see.


Its not quite pure stretch any more. There are a couple of backports installed (virtualbox, libreoffice) this shouldn't affect Network manager. I did try this before adding the backports yesterday and it was the same problem then too.
Mike
 
Posts: 57
Joined: 2005-11-16 19:12
Location: Sunshine Coast, BC

Re: NetworkManager issues

Postby L_V » 2018-10-08 21:48

networking.service should not be active with NetworkManager.
Can you try to disable it ?
Code: Select all
# systemctl disable --now networking.service
# systemctl restart NetworkManager.service
L_V
 
Posts: 799
Joined: 2007-03-19 09:04

Re: NetworkManager issues

Postby Mike » 2018-10-08 22:08

L_V wrote:networking.service should not be active with NetworkManager.
Can you try to disable it ?
Code: Select all
# systemctl disable --now networking.service
# systemctl restart NetworkManager.service


Same issue with networking.service disabled.
Mike
 
Posts: 57
Joined: 2005-11-16 19:12
Location: Sunshine Coast, BC

Re: NetworkManager issues

Postby Mike » 2018-10-08 22:45

This is a bit interesting since I am using an ASUS USB-N53 dongle.

https://bugs.debian.org/cgi-bin/bugrepo ... =842422#10
Mike
 
Posts: 57
Joined: 2005-11-16 19:12
Location: Sunshine Coast, BC

Re: NetworkManager issues

Postby Mike » 2018-10-08 23:46

Disabled predictable naming by masking udevs link file. Now Network-Manager works.

Code: Select all
ln -s /dev/null /etc/systemd/network/99-default.link
Mike
 
Posts: 57
Joined: 2005-11-16 19:12
Location: Sunshine Coast, BC

Re: [SOLVED] NetworkManager issues

Postby L_V » 2018-10-09 07:49

Sorry but I don't think you can call this a "solution", but more a really weird unclear workaround.

"/etc/systemd/network/99-default.link" should not exist.
The systemd’s predictable network names are defined by /lib/systemd/network/99-default.link

Code: Select all
[Link]
NamePolicy=kernel database onboard slot path
MACAddressPolicy=persistent

I would have investigated differently by digging into the udev rules.
Then keep in mind that you can have new surprises later on.

Just to see:
Code: Select all
lsmod |grep ^rt
nmcli d
apt-cache policy network-manager | head -n2
cat /etc/NetworkManager/NetworkManager.conf
lsinitramfs /boot/initrd.img-$(uname -r) | grep net
L_V
 
Posts: 799
Joined: 2007-03-19 09:04

Re: [SOLVED] NetworkManager issues

Postby bw123 » 2018-10-09 12:07

All of the solutions I have seen for this type of nm problem are very weird unclear workarounds. I'm hopeful that people will find out why it is so inconsistent with different hardware and fix it eventually, or replace it with a better tool.
User avatar
bw123
 
Posts: 3400
Joined: 2011-05-09 06:02
Location: TN_USA

Re: [SOLVED] NetworkManager issues

Postby L_V » 2018-10-09 14:39

I cannot believe one second that creating a null link on a file unused by Stretch can be a solution or even a workaround.
The problem is not NetworkManager, but udev, /lib/systemd/network/99-default.link being provided by udev.

Default network name can be defined on different criteria, and the history of the system over the time, through system updates in /usr/lib/udev/rules.d/ can be the problem for an old network USB device.
I don"t think Mike has a clean Stretch.
I see at least 4 solutions or workarounds, but not creating a null link not used by Stretch.
Then if Mike is happy with this weird let's say "solution", all is fine....
L_V
 
Posts: 799
Joined: 2007-03-19 09:04

Re: [SOLVED] NetworkManager issues

Postby Mike » 2018-10-09 19:52

L_V wrote:I cannot believe one second that creating a null link on a file unused by Stretch can be a solution or even a workaround.
The problem is not NetworkManager, but udev, /lib/systemd/network/99-default.link being provided by udev.

Default network name can be defined on different criteria, and the history of the system over the time, through system updates in /usr/lib/udev/rules.d/ can be the problem for an old network USB device.
I don"t think Mike has a clean Stretch.
I see at least 4 solutions or workarounds, but not creating a null link not used by Stretch.
Then if Mike is happy with this weird let's say "solution", all is fine....


The system really doesn't have much history over time.... this installation is only a day old, and it is only using stretch repos and a couple of packages installed from stretch backports. So in terms of debian installs its actually what I would consider very clean install of stretch. There are actually very little in the way of applications installed at this point.

All the link does is masks Predictable Network Interface Names as documented here. https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ and here https://wiki.archlinux.org/index.php/Network_configuration#Revert_to_traditional_interface_names

The result is with Predictable interface names enabled = borkage, and disabled it works. This may be specific to the rt2800 driver. You can toggle the borkage just by add / removing the link.

Just out of curiosity even though the system is pretty clean now, I'll install a minimal stretch with no backports to confirm. I have loads of drive space so its not that big of a job to have another installation.
Mike
 
Posts: 57
Joined: 2005-11-16 19:12
Location: Sunshine Coast, BC

Re: [SOLVED] NetworkManager issues

Postby bw123 » 2018-10-09 20:12

Mike wrote:
L_V wrote:I cannot believe one second that creating a null link on a file unused by Stretch can be a solution or even a workaround.

The problem is not NetworkManager, but udev, /lib/systemd/network/99-default.link being provided by udev.
<snip>
Just out of curiosity even though the system is pretty clean now, I'll install a minimal stretch with no backports to confirm. I have loads of drive space so its not that big of a job to have another installation.


Thanks Mike, I found the same thing to be true when using several older devices, ralink, realtek, also the b43.
Disabling predictable names either thru the null link for 99-default.link or net.ifnames=0 kernel parameter, fixes the issue.

Turning off MAC randomization while scanning also fixes my issues, BTW> the two things seem related.
User avatar
bw123
 
Posts: 3400
Joined: 2011-05-09 06:02
Location: TN_USA

Next

Return to System configuration

Who is online

Users browsing this forum: No registered users and 5 guests

fashionable