You are not logged in.

#1 2020-05-06 16:42:03

louisdm31
Member
Registered: 2020-05-06
Posts: 2

network failures after package upgrades

Hi everybody,

As I recently upgraded my packages, I started experiencing some issues with my network connectivity.
The network (ethernet or wifi) stops and starts again every 5 seconds, and is barely usable.

I checked "systemctl status dhcpcd" and I noticed some strange messages :

pid 0 deleted route to 2a01:e0a:352:e000::/64       (here)
pid 5867 deleted default route via 192.168.0.254
pid 5867 deleted route to 192.168.0.0/24
pid 5867 deleted IP address 192.168.0.23/24     (up to here)
rebinding lease of 192.168.0.23
probing address 192.168.0.23/24
leased 192.168.0.23 for 43200 seconds
adding route to 192.168.0.0/24
adding default route via 192.168.0.254
adding route to 2a01:e0a:352:e000::/64

The issue disappears when I restart NetworkManager over and over again, but comes back as I reboot or resume.

I also copy the messages of "systemctl status NetworkManager" just in case

dhcp4 (eno1): option subnet_mask          => '255.255.255.0'
dhcp4 (eno1): state changed unknown -> bound
device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
manager: NetworkManager state is now CONNECTED_LOCAL
manager: NetworkManager state is now CONNECTED_SITE
policy: set 'eno1' (eno1) as default for IPv4 routing and DNS
device (eno1): Activation: successful, device activated.
manager: NetworkManager state is now CONNECTED_GLOBAL

I tried googling strange messages of dhcpcd, I tried downgrading packages ...
Do you have any idea about what's going on ?

Thanks a lot !!

Offline

#2 2020-05-06 17:00:18

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 7,620

Re: network failures after package upgrades

Why are you running dhcpcd and networkmanager? You pick one or the other, not both.

NM can use other dhcp daemons itself, but the package dropped support for dhcpcd, so it can't be what's starting it.

Offline

#3 2020-05-06 17:24:25

louisdm31
Member
Registered: 2020-05-06
Posts: 2

Re: network failures after package upgrades

Thanks for your answer !
I stopped dhcpcd and now the issue seems to be solved.
Actually, I enabled dhcpcd in addition of NM because that solved a network issue I had in the past.

Offline

Board footer

Powered by FluxBB