Arch Linux

Foucal

Member

Registered: 2022-04-13

Posts: 4

[SOLVED] Ethernet and wifi connection going up and down

Hi,

After an update 3 weeks ago, I happen to have connection issues with my laptop, ie wifi connection slowing down to 0kbit in download, then going back to normal speed, then going back to 0, like a sinusoide. Thinking it was a wpa_supplicant problem, I followed instructions on that link (https://bbs.archlinux.org/viewtopic.php?id=266956), and also installed and configured iwd, without success. After configuration stated in the wiki (https://wiki.archlinux.org/title/Networ … Fi_backend), I was constantly loosing connection within a couple of seconds, and NetworkManager wasn't able to reconnect.
Now, onto my desktop, I'm having the same issue since an update 3 days ago : my connection (via ethernet through PLC) goes to 0kbits for several seconds, and then goes back to normal speed for a minute, then 0kbits, etc. Other computers on windows connected to the internet box (ethernet and wifi) don't have this issue, so it doesn't come from the box. I tried going back to older packages after update but it didn't change anything, I still have those issues. Already rebooted the router twice, not better.

The thing is that I am a bit confused because I don't know if the issue on my laptop is the same as on my desktop : I read there was a wifi problem in the most recent lts kernel update, but I don't understand why my laptop had it 2 weeks before my desktop as I update both of them at the same time, everytime. I already tried to use linux kernel instead of lts but it doesn't change anything. I looked at different posts in this forum related to network but it is always about wifi, for instance this : https://bbs.archlinux.org/viewtopic.php?id=275564

journalctl -u NetworkManager

avril 11 08:24:07 ludo-bureau systemd[1]: Starting Network Manager...
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.0876] NetworkManager (version 1.36.4-1) is starting... (for the first time)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.0880] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
avril 11 08:24:08 ludo-bureau systemd[1]: Started Network Manager.
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.0944] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.1064] manager[0x563aa9466040]: monitoring kernel firmware directory '/lib/firmware'.
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.1779] hostname: hostname: using hostnamed
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.1780] hostname: static hostname changed from (none) to "ludo-bureau"
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.1782] dns-mgr[0x563aa9443250]: init: dns=default,systemd-resolved rc-manager=symlink
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.1784] manager[0x563aa9466040]: rfkill: Wi-Fi hardware radio set enabled
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.1784] manager[0x563aa9466040]: rfkill: WWAN hardware radio set enabled
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2066] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-ovs.so)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2077] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-adsl.so)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2259] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-wwan.so)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2293] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-wifi.so)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2371] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-bluetooth.so)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2750] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-team.so)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2757] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2759] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2760] manager: Networking is enabled by state file
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2785] settings: Loaded settings plugin: keyfile (internal)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2880] dhcp-init: Using DHCP client 'internal'
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2881] device (lo): carrier: link connected
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2887] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2912] manager: (enp0s31f6): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2950] settings: (enp0s31f6): created default wired connection 'Connexion filaire 1'
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.2952] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.5104] manager: (enp5s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.5111] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
avril 11 08:24:08 ludo-bureau NetworkManager[549]: <info>  [1649658248.5951] ovsdb: disconnected from ovsdb
avril 11 08:24:10 ludo-bureau NetworkManager[549]: <info>  [1649658250.0549] device (enp5s0): carrier: link connected
avril 11 08:24:10 ludo-bureau NetworkManager[549]: <info>  [1649658250.0555] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
avril 11 08:24:10 ludo-bureau NetworkManager[549]: <info>  [1649658250.0565] policy: auto-activating connection 'Connexion filaire 2' (6705d3bc-92e1-3602-b3d6-5f209114b999)
avril 11 08:24:10 ludo-bureau NetworkManager[549]: <info>  [1649658250.0578] device (enp5s0): Activation: starting connection 'Connexion filaire 2' (6705d3bc-92e1-3602-b3d6-5f209114b999)
avril 11 08:24:10 ludo-bureau NetworkManager[549]: <info>  [1649658250.0580] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
avril 11 08:24:10 ludo-bureau NetworkManager[549]: <info>  [1649658250.0585] manager: NetworkManager state is now CONNECTING
avril 11 08:24:10 ludo-bureau NetworkManager[549]: <info>  [1649658250.0588] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
avril 11 08:24:10 ludo-bureau NetworkManager[549]: <info>  [1649658250.0601] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
avril 11 08:24:10 ludo-bureau NetworkManager[549]: <info>  [1649658250.0610] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.1231] dhcp4 (enp5s0): state changed new lease, address=192.168.1.11
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.1268] device (enp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.1311] device (enp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.1316] device (enp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.1322] manager: NetworkManager state is now CONNECTED_LOCAL
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.1329] manager: NetworkManager state is now CONNECTED_SITE
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.1330] policy: set 'Connexion filaire 2' (enp5s0) as default for IPv4 routing and DNS
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.1463] device (enp5s0): Activation: successful, device activated.
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.1982] policy: set 'Connexion filaire 2' (enp5s0) as default for IPv6 routing and DNS
avril 11 08:24:12 ludo-bureau NetworkManager[549]: <info>  [1649658252.3236] manager: NetworkManager state is now CONNECTED_GLOBAL
avril 11 08:24:14 ludo-bureau NetworkManager[549]: <info>  [1649658254.5082] manager: startup complete
avril 11 08:24:16 ludo-bureau NetworkManager[549]: <info>  [1649658256.7474] agent-manager: agent[0d81942d09253dad,:1.25/org.freedesktop.nm-applet/1000]: agent registered
avril 11 10:12:52 ludo-bureau systemd[1]: Stopping Network Manager...
avril 11 10:12:52 ludo-bureau NetworkManager[549]: <info>  [1649664772.8288] caught SIGTERM, shutting down normally.
avril 11 10:12:52 ludo-bureau NetworkManager[549]: <info>  [1649664772.8671] dhcp4 (enp5s0): canceled DHCP transaction
avril 11 10:12:52 ludo-bureau NetworkManager[549]: <info>  [1649664772.8672] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
avril 11 10:12:52 ludo-bureau NetworkManager[549]: <info>  [1649664772.8672] dhcp4 (enp5s0): state changed no lease
avril 11 10:12:52 ludo-bureau NetworkManager[549]: <info>  [1649664772.8678] manager: NetworkManager state is now CONNECTED_SITE
avril 11 10:12:52 ludo-bureau NetworkManager[549]: <info>  [1649664772.9101] exiting (success)
avril 11 10:12:53 ludo-bureau systemd[1]: NetworkManager.service: Deactivated successfully.
avril 11 10:12:53 ludo-bureau systemd[1]: Stopped Network Manager.
-- Boot a196259db2b04deda018f4cca3e348a8 --
avril 11 10:13:25 ludo-bureau systemd[1]: Starting Network Manager...
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.2966] NetworkManager (version 1.36.4-1) is starting... (for the first time)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.2966] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
avril 11 10:13:25 ludo-bureau systemd[1]: Started Network Manager.
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.3009] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.3133] manager[0x5611e7bf1040]: monitoring kernel firmware directory '/lib/firmware'.
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.3980] hostname: hostname: using hostnamed
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.3980] hostname: static hostname changed from (none) to "ludo-bureau"
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.3982] dns-mgr[0x5611e7bcd350]: init: dns=default,systemd-resolved rc-manager=symlink
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.3984] manager[0x5611e7bf1040]: rfkill: Wi-Fi hardware radio set enabled
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.3984] manager[0x5611e7bf1040]: rfkill: WWAN hardware radio set enabled
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4103] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-ovs.so)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4112] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-adsl.so)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4367] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-wwan.so)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4431] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-wifi.so)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4466] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-bluetooth.so)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4837] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.36.4-1/libnm-device-plugin-team.so)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4842] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4845] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4846] manager: Networking is enabled by state file
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4870] settings: Loaded settings plugin: keyfile (internal)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4982] dhcp-init: Using DHCP client 'internal'
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4983] device (lo): carrier: link connected
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4986] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.4996] manager: (enp0s31f6): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.5022] settings: (enp0s31f6): created default wired connection 'Connexion filaire 1'
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.5022] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.7206] manager: (enp5s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.7213] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
avril 11 10:13:25 ludo-bureau NetworkManager[515]: <info>  [1649664805.8052] ovsdb: disconnected from ovsdb
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2109] device (enp5s0): carrier: link connected
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2114] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2124] policy: auto-activating connection 'Connexion filaire 2' (6705d3bc-92e1-3602-b3d6-5f209114b999)
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2137] device (enp5s0): Activation: starting connection 'Connexion filaire 2' (6705d3bc-92e1-3602-b3d6-5f209114b999)
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2139] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2144] manager: NetworkManager state is now CONNECTING
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2148] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2161] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2168] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2476] dhcp4 (enp5s0): state changed new lease, address=192.168.1.11
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2507] device (enp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2552] device (enp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2556] device (enp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2564] manager: NetworkManager state is now CONNECTED_LOCAL
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2575] manager: NetworkManager state is now CONNECTED_SITE
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2578] policy: set 'Connexion filaire 2' (enp5s0) as default for IPv4 routing and DNS
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.2721] device (enp5s0): Activation: successful, device activated.
avril 11 10:13:27 ludo-bureau NetworkManager[515]: <info>  [1649664807.4020] manager: NetworkManager state is now CONNECTED_GLOBAL
avril 11 10:13:28 ludo-bureau NetworkManager[515]: <info>  [1649664808.7755] policy: set 'Connexion filaire 2' (enp5s0) as default for IPv6 routing and DNS
avril 11 10:13:31 ludo-bureau NetworkManager[515]: <info>  [1649664811.7184] manager: startup complete
avril 11 10:13:34 ludo-bureau NetworkManager[515]: <info>  [1649664814.0151] agent-manager: agent[6444970f953ef361,:1.25/org.freedesktop.nm-applet/1000]: agent registered
avril 11 12:23:57 ludo-bureau NetworkManager[515]: <info>  [1649672637.2880] manager: NetworkManager state is now CONNECTED_SITE
avril 11 12:28:02 ludo-bureau NetworkManager[515]: <info>  [1649672882.4281] manager: NetworkManager state is now CONNECTED_GLOBAL
avril 11 16:13:27 ludo-bureau NetworkManager[515]: <info>  [1649686407.2820] dhcp4 (enp5s0): state changed new lease, address=192.168.1.11
avril 11 19:38:12 ludo-bureau NetworkManager[515]: <info>  [1649698692.3131] manager: NetworkManager state is now CONNECTED_SITE
avril 11 19:38:26 ludo-bureau NetworkManager[515]: <info>  [1649698706.7242] policy: set 'Connexion filaire 2' (enp5s0) as default for IPv6 routing and DNS
avril 11 19:38:27 ludo-bureau NetworkManager[515]: <info>  [1649698707.4506] manager: NetworkManager state is now CONNECTED_GLOBAL

----

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
avahi-dnsconfd.service                   | multi-user.target.wants
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.NetworkManager.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
snapd.socket                             | sockets.target.wants
sshd.service                             | multi-user.target.wants
var-lib-snapd-snap-bare-5.mount          | multi-user.target.wants
var-lib-snapd-snap-citra\x2demu-136.mount | multi-user.target.wants
var-lib-snapd-snap-citra\x2demu-154.mount | multi-user.target.wants
var-lib-snapd-snap-core20-1169.mount     | multi-user.target.wants
var-lib-snapd-snap-core20-1270.mount     | multi-user.target.wants
var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1519.mount | multi-user.target.wants
var-lib-snapd-snap-nightmayr\x2dkf5\x2dqt\x2d5\x2d15\x2d2\x2dcore20-30.mount | multi-user.target.wants
var-lib-snapd-snap-snapd-13640.mount     | multi-user.target.wants
var-lib-snapd-snap-snapd-14295.mount     | multi-user.target.wants
var-lib-snapd-snap-yuzu-521.mount        | multi-user.target.wants
var-lib-snapd-snap-yuzu-522.mount        | multi-user.target.wants
xdg-user-dirs-update.service             | default.target.wants

Thanks !

Last edited by Foucal (2022-04-15 10:54:22)

seth

Member

Registered: 2012-09-03

Posts: 51,165

Re: [SOLVED] Ethernet and wifi connection going up and down

NM cycles between CONNECTED_SITE and CONNECTED_GLOBAL what would be an issue w/ the router, possibly DNS or a routing issue to NMs ping test ( http://ping.archlinux.org/nm-check.txt )

Please post the complete system journal for your desktop and your laptop and try whether using just dhcpcd (on the wired desktop) or disabling NMs connectivity check gets you a more stable connection.

https://wiki.archlinux.org/title/Networ … nnectivity

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Foucal

Member

Registered: 2022-04-13

Posts: 4

Re: [SOLVED] Ethernet and wifi connection going up and down

Hi, sorry for the late response, and thank you for your quick answer.
I have tried what you told me, and disabling NM connectivity checks worked on my laptop, but not on my desktop. So after checking on youtube, twitch and making updates this morning, my laptop seems to have no connection problem anymore. But as you asked, here is the journalctl -b : http://ix.io/3V8n

However, on my desktop it didn't change anything. I also tried using dhcpcd but not better. Here is the journalctl -b : http://ix.io/3V8m

seth

Member

Registered: 2012-09-03

Posts: 51,165

Re: [SOLVED] Ethernet and wifi connection going up and down

avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1055] device (enp5s0): carrier: link connected
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1059] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1066] policy: auto-activating connection 'Connexion filaire 2' (6705d3bc-92e1-3602-b3d6-5f209114b999)
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1074] device (enp5s0): Activation: starting connection 'Connexion filaire 2' (6705d3bc-92e1-3602-b3d6-5f209114b999)
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1075] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1079] manager: NetworkManager state is now CONNECTING
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1082] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1090] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1095] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1240] dhcp4 (enp5s0): state changed new lease, address=192.168.1.11
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1264] device (enp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1303] device (enp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1306] device (enp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1311] manager: NetworkManager state is now CONNECTED_LOCAL
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1315] manager: NetworkManager state is now CONNECTED_SITE
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1316] policy: set 'Connexion filaire 2' (enp5s0) as default for IPv4 routing and DNS
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1415] device (enp5s0): Activation: successful, device activated.
avril 14 12:02:31 ludo-bureau NetworkManager[551]: <info>  [1649930551.1423] manager: NetworkManager state is now CONNECTED_GLOBAL

There's no indication for a network failure - how do you determine such?

ip a
ip r
ping -c1 8.8.8.8
ping -c1 google.com
dig google.com
dig @8.8.8.8 google.com

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Foucal

Member

Registered: 2022-04-13

Posts: 4

Re: [SOLVED] Ethernet and wifi connection going up and down

There's no indication for a network failure - how do you determine such?

I just look at my download speed when I update my system, looking at the abrupt change of quality watching a video or a stream (from 1080p to 144p for instance).

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:14:d1:1e:ac:e8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.11/24 brd 192.168.1.255 scope global dynamic noprefixroute enp5s0
       valid_lft 37411sec preferred_lft 37411sec
    inet6 2a01:e34:ed3d:4170:687e:e0eb:1f46:f63e/64 scope global dynamic noprefixroute 
       valid_lft 86211sec preferred_lft 86211sec
    inet6 fe80::23f7:1e08:1d85:fa90/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 2c:56:dc:4a:81:dd brd ff:ff:ff:ff:ff:ff

ip r

default via 192.168.1.254 dev enp5s0 proto dhcp metric 100 
192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.11 metric 100

ping -c1 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) octets de données.
64 octets de 8.8.8.8 : icmp_seq=1 ttl=115 temps=99.0 ms

--- statistiques ping 8.8.8.8 ---
1 paquets transmis, 1 reçus, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 98.968/98.968/98.968/0.000 ms

ping -c1 google.com

PING google.com(par10s38-in-x0e.1e100.net (2a00:1450:4007:805::200e)) 56 octets de données
64 octets de par10s38-in-x0e.1e100.net (2a00:1450:4007:805::200e) : icmp_seq=1 ttl=119 temps=21.2 ms

--- statistiques ping google.com ---
1 paquets transmis, 1 reçus, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 21.245/21.245/21.245/0.000 ms

I read dig was apparently deprecated so I used drill, I hope it's ok.
drill google.com

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 220
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; google.com.	IN	A

;; ANSWER SECTION:
google.com.	227	IN	A	216.58.204.142

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 507 msec
;; SERVER: fd0f:ee:b0::1
;; WHEN: Thu Apr 14 19:41:55 2022
;; MSG SIZE  rcvd: 44

drill @8.8.8.8 google.com

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 62781
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; google.com.	IN	A

;; ANSWER SECTION:
google.com.	300	IN	A	142.250.186.46

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 23 msec
;; SERVER: 8.8.8.8
;; WHEN: Thu Apr 14 19:42:15 2022
;; MSG SIZE  rcvd: 44

seth

Member

Registered: 2012-09-03

Posts: 51,165

Re: [SOLVED] Ethernet and wifi connection going up and down

You're defaulting to a local IPv6 DNS which according to you first drill doesn't have all to greate response times (508ms …)
Not sure whether that's the problem (the symptoms are too vague, ideally test the performance against some LAN IP, not a streaming service that will break down when your entire neighbourhood flips on netflix…) but becuse of the lousy DNS also see https://wiki.archlinux.org/title/Domain_name_resolution and configure a better™ DNS server and see whether that fixes it.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Foucal

Member

Registered: 2022-04-13

Posts: 4

Re: [SOLVED] Ethernet and wifi connection going up and down

Before trying to check DNS, I tried what I should've tried at the beginning, ie connecting directly my computer in ethernet to the box instead of PLC : it works flawlessly, no speed variation or whatsoever. I didn't think of it before yesterday because I never had any problem with the PLC before. Hence, I will figure out a way to connect directly my desktop to the box and I'm done.

So, thank you very much seth and really sorry for wasting your time (your advice for connectivity check was useful for my laptop though). I should have put this thread in newbie corner apparently...

Last edited by Foucal (2022-04-15 10:55:54)