- Package:
- network-manager
- Source:
- network-manager
- Description:
- network management framework (daemon and userspace tools)
- Submitter:
- Victor Porton
- Date:
- 2021-03-07 12:39:03 UTC
- Severity:
- important
Dear Maintainer, Normally "Network" window shows: - IPv4 Address 10.0.0.8 - IPv6 Address XXX - Hardware Address: XXX - Default Route: 10.0.0.138 - DNS: 10.0.0.138 Sometimes it becomes: - IPv6 Address XXX - Hardware Address: XXX - DNS: 10.0.0.138 So "IPv4 Address" and "Default Route" stop working and the network ceases to work. I updated to network-manager 1.8.2-1 from "buster" in my "stretch" Debian installation, but this hasn't solved the trouble.
I forgot to say that I use a Ethernet-connected-to-my-PC router with DHCP in the router to connect my PC to Internet.
After some upgrades of my Debian Linux "stretch" including sudo apt install -t=stretch-backports evolution network-manager the bug did not disappeared, but now when network disconnects, there is no more visible indication of the bug in Gnome 3 panel. The connection icon (near the top right corner of the screen) remains active (there are no symptoms of disconnection). Otherwise the bug remains the same: I need to disconnect and connect again about every hour of half for the network to work.
Jan 23 05:50:28 victor dhclient[1389]: DHCPREQUEST of 10.0.0.7 on eth0 to 255.255.255.255 port 67 Jan 23 05:50:39 victor dhclient[1389]: DHCPREQUEST of 10.0.0.7 on eth0 to 255.255.255.255 port 67 Jan 23 05:50:52 victor dhclient[1389]: DHCPREQUEST of 10.0.0.7 on eth0 to 255.255.255.255 port 67 Jan 23 05:51:08 victor dhclient[1389]: DHCPREQUEST of 10.0.0.7 on eth0 to 255.255.255.255 port 67 Jan 23 05:51:27 victor dhclient[1389]: DHCPREQUEST of 10.0.0.7 on eth0 to 255.255.255.255 port 67 Jan 23 05:51:42 victor dhclient[1389]: DHCPREQUEST of 10.0.0.7 on eth0 to 255.255.255.255 port 67 Jan 23 05:51:49 victor avahi-daemon[665]: Withdrawing address record for 10.0.0.7 on eth0. Jan 23 05:51:49 victor avahi-daemon[665]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.0.7. Jan 23 05:51:49 victor avahi-daemon[665]: Interface eth0.IPv4 no longer relevant for mDNS. Jan 23 05:51:49 victor NetworkManager[663]: <info> [1516679509.3378] manager: NetworkManager state is now CONNECTED_SITE Jan 23 05:51:49 victor dbus-daemon[647]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus- org.freedesktop.nm-dispatcher.service' requested by ':1 .11' (uid=0 pid=663 comm="/usr/sbin/NetworkManager --no-daemon ") Jan 23 05:51:49 victor systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 23 05:51:49 victor gsd-sharing[2183]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote- desktop.service not loaded. Jan 23 05:51:49 victor dbus-daemon[647]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 23 05:51:49 victor systemd[1]: Started Network Manager Script Dispatcher Service. Jan 23 05:51:49 victor nm-dispatcher: req:1 'connectivity-change': new request (1 scripts) Jan 23 05:51:49 victor nm-dispatcher: req:1 'connectivity-change': start running ordered scripts... Jan 23 05:51:50 victor NetworkManager[663]: <info> [1516679510.2724] dhcp4 (eth0): state changed bound -> expire Jan 23 05:51:50 victor NetworkManager[663]: <info> [1516679510.3046] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 1389 Jan 23 05:51:50 victor NetworkManager[663]: <info> [1516679510.3046] dhcp4 (eth0): state changed expire -> done Jan 23 05:51:50 victor NetworkManager[663]: <info> [1516679510.3049] device (eth0): scheduling DHCPv4 restart in 120 seconds, 3 tries left (reason: lease expired)
From journalctl output (attached). It seems that DHCP lease expires and after that DHCP does not start work again. Why? Help me to make my network stable!!!
Hello kind people of Debian, reportbug did not ask me for the relevant journalctl entry... so here it is attached. I am a Debian sysadmin (not a developer sorry). This is on my personal MacBookPro. paul
Dear Maintainer,
* What led up to the situation?
The disconnecting and reconnecting of the wifi happened also in the past (several months ago), but suddenly stopped. I update Debian every day. Some two weeks ago it started again. This is the same computer for three years now, same wifi, same location, same modem/router, same ISP, nothing changes except for the aptitude upgrade.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I googled the problem a lot the past few days.
I added "wifi,powersafe=2' to NetworkManager.conf (because this is suggested in a forum).
I reinstalled broadcom-sta-dkms.
Yesterday I uninstalled dhclient (isc-dhcp-client), but that also makes no difference.
I upgrade Debian every day.
* What was the outcome of this action?
No difference, the wifi keeps disconnecting (and reconnecting) often.
* What outcome did you expect instead?
A stable wifi connection, these interrupts are distracting.
Hello kind people of Debian, I think this attachment may also be of interest. It is the output of journalctl | grep CTRL-EVENT-DISCONNECTED | tail -30 It shows the disconnects interval, which is often (but not always) close to one hour. That's why I though DHCP lease time and uninstalled isc-dhcp-client. It didn't help. paul
The problem seems solved. I changed the ipv6 settings in the NetworkManager GUI to use EUI64 and now there are no more disconnects. (I also kept doing aptitude update && aptitude upgrade daily.) paul