In the last two months it happens sometimes that from time to time my internet connection gets so slow that i either have to restart the router, restart NetworkManager or restart the machine entirely.
These solutions give me some minutes of full speed, but then I have to do it again and this is getting pretty frustrating.
I have tried changing kernels (5.12, 5.10, 5.4) with no luck.
This is my inxi, if other info is needed please feel free to ask
System: Host: cocco Kernel: 5.4.124-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.22.3 Distro: Manjaro Linux
Machine: Type: Laptop System: LENOVO product: 20354 v: Lenovo Z50-70 serial:
Mobo: LENOVO model: Lancer 5A5 v: 31900058WIN serial: UEFI: LENOVO v: 9BCN26WW
date: 07/31/2014
Battery: ID-1: BAT0 charge: 22.2 Wh (100.0%) condition: 22.2/41.4 Wh (53.5%)
CPU: Info: Dual Core model: Intel Core i7-4510U bits: 64 type: MT MCP cache: L2: 4 MiB
Speed: 976 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 976 2: 925 3: 1036 4: 1050
Graphics: Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
Device-2: NVIDIA GM108M [GeForce 840M] driver: nvidia v: 465.31
Device-3: Acer Lenovo EasyCamera type: USB driver: uvcvideo
Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting,nvidia resolution: 1920x1080~60Hz
OpenGL: renderer: N/A v: N/A
Audio: Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel
Device-2: Intel 8 Series HD Audio driver: snd_hda_intel
Sound Server-1: ALSA v: k5.4.124-1-MANJARO running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8168
IF: enp1s0 state: down mac: 28:d2:44:ef:b5:57
Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be
IF: wlp2s0 state: up mac: da:00:11:55:d0:9a
Bluetooth: Device-1: Realtek RTL8723B Bluetooth type: USB driver: btusb
Report: rfkill ID: hci0 state: up address: see --recommends
Drives: Local Storage: total: 931.51 GiB used: 393.97 GiB (42.3%)
ID-1: /dev/sda vendor: Seagate model: ST1000LM014-SSHD-8GB size: 931.51 GiB
Partition: ID-1: / size: 819.77 GiB used: 344.22 GiB (42.0%) fs: ext4 dev: /dev/sda5
ID-2: /boot/efi size: 96 MiB used: 25.3 MiB (26.3%) fs: vfat dev: /dev/sda1
Swap: Alert: No swap data was found.
Sensors: System Temperatures: cpu: 51.0 C mobo: N/A gpu: nvidia temp: 46 C
Fan Speeds (RPM): N/A
Info: Processes: 213 Uptime: 43m Memory: 15.53 GiB used: 5.27 GiB (33.9%) Shell: Bash inxi: 3.3.05
Didn’t think somebody will ever complain about this, since I think it’s perfectly normal. In my case it always happens when it’s time to re-lease, like this:
Jun 23 19:33:54 Lelesus NetworkManager[914]: <info> [1624451634.3024] device (wlan0): DHCPv4 lease renewal requested
Jun 23 19:33:54 Lelesus NetworkManager[914]: <info> [1624451634.3193] dhcp4 (wlan0): canceled DHCP transaction
Jun 23 19:33:54 Lelesus NetworkManager[914]: <info> [1624451634.3193] dhcp4 (wlan0): state changed bound -> terminated
Jun 23 19:33:54 Lelesus NetworkManager[914]: <info> [1624451634.3196] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jun 23 19:33:54 Lelesus NetworkManager[914]: <info> [1624451634.3203] device (wlan0): supplicant interface state: authenticating -> associating
Jun 23 19:33:54 Lelesus NetworkManager[914]: <info> [1624451634.3203] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Jun 23 19:33:54 Lelesus NetworkManager[914]: <info> [1624451634.3494] device (wlan0): supplicant interface state: associating -> associated
Jun 23 19:33:54 Lelesus NetworkManager[914]: <info> [1624451634.3495] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.5835] device (wlan0): supplicant interface state: associated -> disconnected
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.5836] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.6837] device (wlan0): supplicant interface state: disconnected -> scanning
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.6837] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.7907] device (wlan0): supplicant interface state: scanning -> authenticating
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.7907] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.7922] device (wlan0): supplicant interface state: authenticating -> associating
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.7922] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8046] device (wlan0): supplicant interface state: associating -> associated
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8046] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8046] device (wlan0): DHCPv4 lease renewal requested
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8296] dhcp4 (wlan0): canceled DHCP transaction
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8297] dhcp4 (wlan0): state changed unknown -> terminated
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8300] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8305] device (wlan0): supplicant interface state: associated -> 4way_handshake
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8305] device (p2p-dev-wlan0): supplicant management interface state: associated -> 4way_handshake
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8336] device (wlan0): supplicant interface state: 4way_handshake -> completed
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8349] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Jun 23 19:34:00 Lelesus NetworkManager[914]: <info> [1624451640.8505] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.8.112
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5401] device (wlan0): supplicant interface state: completed -> authenticating
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5401] device (p2p-dev-wlan0): supplicant management interface state: completed -> authenticating
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5407] device (wlan0): DHCPv4 lease renewal requested
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5573] dhcp4 (wlan0): canceled DHCP transaction
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5573] dhcp4 (wlan0): state changed bound -> terminated
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5577] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5587] device (wlan0): supplicant interface state: authenticating -> associating
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5587] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5764] device (wlan0): supplicant interface state: associating -> associated
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.5764] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.6724] device (wlan0): supplicant interface state: associated -> 4way_handshake
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.6724] device (p2p-dev-wlan0): supplicant management interface state: associated -> 4way_handshake
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.6854] device (wlan0): supplicant interface state: 4way_handshake -> completed
Jun 24 19:34:01 Lelesus NetworkManager[914]: <info> [1624538041.6909] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Jun 24 19:34:03 Lelesus NetworkManager[914]: <info> [1624538043.7568] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.8.112
Jun 25 00:01:52 Lelesus NetworkManager[914]: <info> [1624554112.5726] manager: NetworkManager state is now CONNECTED_SITE
Jun 25 00:10:23 Lelesus NetworkManager[914]: <info> [1624554623.9451] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 25 00:25:35 Lelesus NetworkManager[914]: <info> [1624555535.5166] manager: NetworkManager state is now CONNECTED_SITE
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6523] device (wlan0): supplicant interface state: completed -> authenticating
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6523] device (p2p-dev-wlan0): supplicant management interface state: completed -> authenticating
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6526] device (wlan0): DHCPv4 lease renewal requested
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6869] dhcp4 (wlan0): canceled DHCP transaction
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6869] dhcp4 (wlan0): state changed bound -> terminated
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6874] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6885] device (wlan0): supplicant interface state: authenticating -> associating
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6885] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6886] device (wlan0): supplicant interface state: associating -> 4way_handshake
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6886] device (p2p-dev-wlan0): supplicant management interface state: associating -> 4way_handshake
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6887] device (wlan0): supplicant interface state: 4way_handshake -> completed
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.6892] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.7290] dhcp4 (wlan0): state changed unknown -> expire
Jun 25 05:50:03 Lelesus NetworkManager[914]: <info> [1624575003.7290] device (wlan0): DHCPv4: trying to acquire a new lease within 90 seconds
Jun 25 05:50:04 Lelesus NetworkManager[914]: <info> [1624575004.0194] dhcp4 (wlan0): state changed expire -> bound, address=192.168.8.112
Jun 25 08:53:11 Lelesus NetworkManager[914]: <info> [1624585991.0183] audit: op="statistics" arg="refresh-rate-ms" pid=117269 uid=1000 result="success"
Jun 25 08:53:11 Lelesus NetworkManager[914]: <info> [1624585991.0214] audit: op="statistics" arg="refresh-rate-ms" pid=117288 uid=1000 result="success"
Jun 25 08:53:18 Lelesus NetworkManager[914]: <info> [1624585998.6535] audit: op="statistics" arg="refresh-rate-ms" pid=117269 uid=1000 result="success"
Jun 25 08:53:18 Lelesus NetworkManager[914]: <info> [1624585998.6572] audit: op="statistics" arg="refresh-rate-ms" pid=117288 uid=1000 result="success"
You can read how many times it has to re-issue the request before finally bound to a new (but sometimes old, this is router configuration dependent) ip address. I can’t really pinpoint where the issue is, but a quick “fix” is to increase lease time so the renewal time is way longer than it is now. Make it like 2 weeks or 1 month, maybe?
I don’t think that this is the problem. Restarting NM sometimes grants me around 20m of usable internet, sometimes 2, this is way too inconsistent to look like a ip lease problem. For now i will also try using a static ip address
Update after a week:
I’m not convinced that the issue is just a protocol thing of the PC asking a new address, but setting a static IP addrss in NM seems to have fixed the problem