Internet Latency Problems Fedora 41

isudoajl · March 10, 2025, 4:55pm

Hello experts,

Im using Fedora since F35 I think, and its the first time that Im experimenting latency problems.

As always, I install each new version from scratch, I never upgrade.

System:
  Kernel: 6.13.5-200.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: GNOME v: 47.4 tk: GTK v: 3.24.43 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 41 (Workstation Edition)
Machine:
  Type: Laptop System: ASUSTeK product: ROG Strix G731GU_G731GU v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: G731GU v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: G731GU.312 date: 02/19/2021
Battery:
  ID-1: BAT0 charge: 41.6 Wh (100.0%) condition: 41.6/66.0 Wh (63.1%)
    volts: 15.7 min: 15.7 model: ASUSTeK ASUS Battery serial: N/A
    status: not charging
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse B330/M330/M331
    serial: <filter> charge: 55% (should be ignored) status: discharging
CPU:
  Info: 6-core model: Intel Core i7-9750H bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 384 KiB L2: 1.5 MiB L3: 12 MiB
  Speed (MHz): avg: 900 min/max: 800/4500 cores: 1: 900 2: 900 3: 900 4: 900
    5: 900 6: 900 7: 900 8: 900 9: 900 10: 900 11: 900 12: 900 bogomips: 62399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: none
    bus-ID: 00:02.0 chip-ID: 8086:3e9b
  Device-2: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] vendor: ASUSTeK
    driver: nvidia v: 570.86.16 arch: Turing pcie: speed: 2.5 GT/s lanes: 8
    ports: active: none empty: DP-1,HDMI-A-1 bus-ID: 01:00.0
    chip-ID: 10de:2191
  Display: wayland server: Xwayland v: 24.1.6 compositor: gnome-shell
    driver: gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics 0x409d res: 1920x1080 dpi: 128
    diag: 438mm (17.3")
  API: OpenGL v: 4.6 vendor: intel mesa v: 25.0.0 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    device-ID: 8086:3e9b display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo gpu: nvidia-settings x11: xdriinfo, xdpyinfo,
    xprop, xrandr
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a348
  Device-2: NVIDIA TU116 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 10de:1aeb
  API: ALSA v: k6.13.5-200.fc41.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:a370
  IF: wlo1 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168
  IF: eno2 state: down mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-14:4
    chip-ID: 8087:0aaa
  Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.1
    lmp-v: 10
Drives:
  Local Storage: total: 2.96 TiB used: 178.93 GiB (5.9%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN520
    SDAPNUW-256G-1002 size: 238.47 GiB speed: 15.8 Gb/s lanes: 2
    serial: <filter> temp: 33.9 C
  ID-2: /dev/sda vendor: Seagate model: ST1000LX015-1U7172 size: 931.51 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 31 C
  ID-3: /dev/sdb vendor: Western Digital model: WD Elements SE SSD
    size: 931.51 GiB type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 serial: <filter>
  ID-4: /dev/sdc vendor: SanDisk model: Portable SSD size: 931.51 GiB
    type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 102.71 GiB used: 21.49 GiB (20.9%) fs: btrfs
    dev: /dev/nvme0n1p6
  ID-2: /boot size: 973.4 MiB used: 371.8 MiB (38.2%) fs: ext4
    dev: /dev/nvme0n1p5
  ID-3: /boot/efi size: 96 MiB used: 44.6 MiB (46.5%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 102.71 GiB used: 21.49 GiB (20.9%) fs: btrfs
    dev: /dev/nvme0n1p6
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 1024 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.0 C pch: 54.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 2500
Info:
  Memory: total: 16 GiB available: 15.46 GiB used: 7.67 GiB (49.6%)
  Processes: 456 Power: uptime: 4h 21m wakeups: 0 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 57
    Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.32 running-in: ptyxis-agent
    inxi: 3.3.37

Guys, do you know anything about this?

barryascott · March 10, 2025, 5:02pm

How are you measuring latency?
Can you test a wired connection to your router to compare wifi to wired?

isudoajl · March 10, 2025, 6:50pm

Thanks for your time @barryascott

ping google.com

I have taken your advice and with cable it does NOT present anomalies.

A little more of context:
I first noticed this while browsing, sometimes everything was normal 10ms - 20ms (max) and other times with lags from 100ms to 6000ms at random.

When I measured the latency using ping google.com I was able to corroborate this anomaly.

Actions taken so far:
Action: Tip: Lower WiFi latency by disabling WiFi power management
Results: No positive results

computersavvy · March 11, 2025, 2:36am

I have almost the same laptop. The only differences I see are

Mine shows G731GU-GL731GU
Same firmware version and date.
You have a 3TB drive and I have the 500GB
At the end you show flatpak pkgs: 57 and I only show 18.
Otherwise the systems appear identical.

I have never seem any latency with internet, and using the ookla speed test (www.speedtest.net) I show download 580+Mbps and upload of 640+Mbps (test just run as I am writing this). I am on a frontier fibre connection rated at 1Gbps

I suspect any latency you are seeing may be related to either your location or your ISP and not either the laptop or fedora.

Note that the router itself is also a factor in internet speeds, as well as the wifi band used (2.4 GHz vs 5 GHz) (even the channel within the band can be a factor) since those bands operate at different speeds. Other users in the area may be using the same wifi band/channel which can affect overall speeds. The gnome wifi settings should show the band used.

ledeni · March 11, 2025, 2:50am

Disable ipv6 for your wifi connection It’s by default auto and see how is going with internet connection

isudoajl · March 11, 2025, 11:04am

Thanks for your time.

This is an script that output latency > 100ms

user@workstation:~$ source test.sh 
[2025-03-11 10:07:23] Warning: Ping time over 100ms! (128 ms)
[2025-03-11 10:07:39] Warning: Ping time over 100ms! (127 ms)
[2025-03-11 10:08:24] Warning: Ping time over 100ms! (114 ms)
[2025-03-11 10:08:38] Warning: Ping time over 100ms! (132 ms)
[2025-03-11 10:08:55] Warning: Ping time over 100ms! (129 ms)
[2025-03-11 10:09:22] Warning: Ping time over 100ms! (119 ms)
[2025-03-11 10:09:41] Warning: Ping time over 100ms! (124 ms)
[2025-03-11 10:09:53] Warning: Ping time over 100ms! (131 ms)
[2025-03-11 10:09:55] Warning: Ping time over 100ms! (124 ms)
[2025-03-11 10:10:23] Warning: Ping time over 100ms! (119 ms)
[2025-03-11 10:11:43] Warning: Ping time over 100ms! (112 ms)
[2025-03-11 10:12:26] Warning: Ping time over 100ms! (122 ms)
[2025-03-11 10:12:38] Warning: Ping time over 100ms! (113 ms)
[2025-03-11 10:12:41] Warning: Ping time over 100ms! (124 ms)
[2025-03-11 10:12:54] Warning: Ping time over 100ms! (123 ms)
[2025-03-11 10:13:24] Warning: Ping time over 100ms! (139 ms)
[2025-03-11 10:14:24] Warning: Ping time over 100ms! (126 ms)
[2025-03-11 10:14:54] Warning: Ping time over 100ms! (120 ms)
[2025-03-11 10:15:52] Warning: Ping time over 100ms! (101 ms)
[2025-03-11 10:17:23] Warning: Ping time over 100ms! (126 ms)
[2025-03-11 10:19:55] Warning: Ping time over 100ms! (130 ms)
[2025-03-11 10:20:09] Warning: Ping time over 100ms! (131 ms)
[2025-03-11 10:20:42] Warning: Ping time over 100ms! (131 ms)
[2025-03-11 10:21:23] Warning: Ping time over 100ms! (131 ms)
[2025-03-11 10:21:52] Warning: Ping time over 100ms! (103 ms)
[2025-03-11 10:21:53] Warning: Ping time over 100ms! (118 ms)
[2025-03-11 10:22:55] Warning: Ping time over 100ms! (130 ms)
[2025-03-11 10:23:56] Warning: Ping time over 100ms! (113 ms)
[2025-03-11 10:25:42] Warning: Ping time over 100ms! (125 ms)
[2025-03-11 10:26:33] Warning: Ping time over 100ms! (115 ms)
[2025-03-11 10:26:38] Warning: Ping time over 100ms! (127 ms)
[2025-03-11 10:27:22] Warning: Ping time over 100ms! (102 ms)
[2025-03-11 10:28:07] Warning: Ping time over 100ms! (106 ms)
[2025-03-11 10:28:08] Warning: Ping time over 100ms! (131 ms)
[2025-03-11 10:28:47] Warning: Ping time over 100ms! (137 ms)

I have another laptop with Fedora server and another one with windows (Wireless) and both not present this anomaly.

But with wire connected this not happen:

user@workstation:~$ source test.sh

Basically not output.

Latency with wire:

user@workstation:~$ ping google.com
PING google.com (2a00:1450:4003:800::200e) 56 data bytes
64 bytes from mad41s04-in-x0e.1e100.net (2a00:1450:4003:800::200e): icmp_seq=1 ttl=60 time=13.7 ms
64 bytes from mad41s04-in-x0e.1e100.net (2a00:1450:4003:800::200e): icmp_seq=2 ttl=60 time=14.1 ms
64 bytes from mad41s04-in-x0e.1e100.net (2a00:1450:4003:800::200e): icmp_seq=3 ttl=60 time=14.0 ms
64 bytes from mad41s04-in-x0e.1e100.net (2a00:1450:4003:800::200e): icmp_seq=4 ttl=60 time=13.8 ms
64 bytes from mad41s04-in-x0e.1e100.net (2a00:1450:4003:800::200e): icmp_seq=5 ttl=60 time=14.0 ms
64 bytes from mad41s04-in-x0e.1e100.net (2a00:1450:4003:800::200e): icmp_seq=6 ttl=60 time=14.0 ms

isudoajl · March 11, 2025, 11:05am

Thanks for your time.

I try your advice, but same problem.

computersavvy · March 11, 2025, 12:51pm

Your test results seem to clearly show this is a wifi issue.

You might scan to see how many users are on the band/channel your laptop is using, and even try a different channel. This is quite often an issue when a channel is heavily used by nearby systems.

You have stated that the latency varies intermittently – which is another indication that it probably is influenced by congestion on the channel being used.

My area is not congested with a considerable spacing between residences and only 5 other wifi users show up with a scan.

isudoajl · March 11, 2025, 5:35pm

Mine is lozadaNETwork

IN-USE  BSSID              SSID                      MODE   CHAN  RATE        SIGNAL  BARS  SECURITY  
lines 1-1...skipping...
IN-USE  BSSID              SSID                      MODE   CHAN  RATE        SIGNAL  BARS  SECURITY  
        C4:FB:AA:14:79:C8  lozadaNETwork             Infra  3     260 Mbit/s  94      ▂▄▆█  WPA2      
lines 1-2...skipping...
IN-USE  BSSID              SSID                      MODE   CHAN  RATE        SIGNAL  BARS  SECURITY  
        C4:FB:AA:14:79:C8  lozadaNETwork             Infra  3     260 Mbit/s  94      ▂▄▆█  WPA2      
*       C4:FB:AA:14:79:CC  lozadaNETwork             Infra  36    540 Mbit/s  94      ▂▄▆█  WPA2      
        90:F9:B7:AD:46:30  Vodafone-AD4623           Infra  100   540 Mbit/s  70      ▂▄▆_  WPA2      
        90:F9:B7:AD:46:2C  Vodafone-AD4623           Infra  10    260 Mbit/s  62      ▂▄▆_  WPA2      
lines 1-5...skipping...
IN-USE  BSSID              SSID                      MODE   CHAN  RATE        SIGNAL  BARS  SECURITY  
        C4:FB:AA:14:79:C8  lozadaNETwork             Infra  3     260 Mbit/s  94      ▂▄▆█  WPA2      
*       C4:FB:AA:14:79:CC  lozadaNETwork             Infra  36    540 Mbit/s  94      ▂▄▆█  WPA2      
        90:F9:B7:AD:46:30  Vodafone-AD4623           Infra  100   540 Mbit/s  70      ▂▄▆_  WPA2      
        90:F9:B7:AD:46:2C  Vodafone-AD4623           Infra  10    260 Mbit/s  62      ▂▄▆_  WPA2      
        A0:1C:8D:E6:08:98  Vodafone-E60890           Infra  4     195 Mbit/s  50      ▂▄__  WPA1 WPA2 
        1C:AB:C0:D1:D2:F8  NOS-D2F0                  Infra  12    130 Mbit/s  47      ▂▄__  WPA1 WPA2 
        A0:1C:8D:E6:08:9C  Vodafone-E60890           Infra  44    540 Mbit/s  44      ▂▄__  WPA1 WPA2 
        FC:77:7B:E5:67:06  NOS-6706                  Infra  11    260 Mbit/s  30      ▂___  WPA2      
lines 1-9...skipping...
IN-USE  BSSID              SSID                      MODE   CHAN  RATE        SIGNAL  BARS  SECURITY  
        C4:FB:AA:14:79:C8  lozadaNETwork             Infra  3     260 Mbit/s  94      ▂▄▆█  WPA2      
*       C4:FB:AA:14:79:CC  lozadaNETwork             Infra  36    540 Mbit/s  94      ▂▄▆█  WPA2      
        90:F9:B7:AD:46:30  Vodafone-AD4623           Infra  100   540 Mbit/s  70      ▂▄▆_  WPA2      
        90:F9:B7:AD:46:2C  Vodafone-AD4623           Infra  10    260 Mbit/s  62      ▂▄▆_  WPA2      
        A0:1C:8D:E6:08:98  Vodafone-E60890           Infra  4     195 Mbit/s  50      ▂▄__  WPA1 WPA2 
        1C:AB:C0:D1:D2:F8  NOS-D2F0                  Infra  12    130 Mbit/s  47      ▂▄__  WPA1 WPA2 
        A0:1C:8D:E6:08:9C  Vodafone-E60890           Infra  44    540 Mbit/s  44      ▂▄__  WPA1 WPA2 
        FC:77:7B:E5:67:06  NOS-6706                  Infra  11    260 Mbit/s  30      ▂___  WPA2      
        FC:73:FB:9A:59:2C  Vodafone-9A5921           Infra  100   540 Mbit/s  25      ▂___  WPA2      
        D8:10:9F:71:27:08  Vodafone-7126FB           Infra  100   540 Mbit/s  25      ▂___  WPA2      
        FC:73:FB:9A:59:28  Vodafone-9A5921           Infra  6     260 Mbit/s  22      ▂___  WPA2      
        FA:8F:CA:72:96:77  Polk MagniFi Mini-5286.d  Infra  1     130 Mbit/s  20      ▂___  --        
lines 1-13

Overview
Looking at your scan results, let me analyze the channel congestion:

Your network “lozadaNETwork” is broadcasting on:

Channel 3 (2.4GHz) with signal strength 94% (▂▄▆█)
Channel 36 (5GHz) with signal strength 94% (▂▄▆█) - This is the one you’re currently using (marked with )

Other networks nearby:

Vodafone-AD4623 on:

Channel 100 (5GHz)
Channel 10 (2.4GHz)

Channel congestion analysis:

2.4GHz band:

Your network is on channel 3
Another network on channel 10
This is relatively good spacing in the 2.4GHz band, not much overlap

5GHz band:

Your network is on channel 36
The other network is on channel 100
This is excellent spacing in the 5GHz band, no overlap at all

Based on this scan, your channel selection is actually quite good:

The channels you’re using (3 and 36) have good separation from other networks
Signal strength is excellent (94% on both bands)
There’s minimal channel overlap with other networks

The channel congestion does NOT appear to be the cause of your latency issues, as:

There are relatively few networks in your area
The channels are well-separated
Your signal strength is excellent
There’s minimal interference from overlapping channels

Thoughts:
In the end, I don’t think it’s worth your time with this issue; I’ve never experienced this since I started using F35… until F41. Anyway, thank you all very much for your time.

isudoajl · March 14, 2025, 2:13pm

SOLUTION:

I was able to determine that the conflict was caused at kernel side, with an wrong generated configuration file when making the setup of the KVM using an ansible playbook to populate the conf file ==> /etc/polkit-1/rules.d/50-libvirt.rules.

The issue was so severe that it got into a login loop. I rolled back and installed F40 and ran all my Ansible playbooks to configure my machine. When I rebooted, I was able to log in, but everything disappeared from my desktop.

What was new here? I had migrated all my sh scripts to Ansible playbooks. I reviewed them one by one, and the ones I paid most attention to were the video and KVM ones, and I was able to detect the problem.

Just for information purposes, that was the content conf file:

polkit_rule: |
polkit.addRule(function(action, subject) {
if (action.id == "org.libvirt.unix.manage" &&
subject.isInGroup("wheel")) {
return polkit.Result.YES;
}
});

The playbook created the file without the quotes, which caused all these conflicts, including the latencies.

Topic		Replies	Views
Keyboard latency with Logitech G915 wireless keyboard Ask Fedora f34 , keyboard , desktop	3	2076	November 8, 2021
Iwlwifi crashes regularly with some APs Ask Fedora wifi , intel , nvidia	3	1304	November 2, 2022
Fedora lagging Ask Fedora f36	2	630	September 15, 2022
Any MSI laptop users that can share their experiences with using Fedora? Ask Fedora	5	1167	October 16, 2024
Quite long boot time compared to windows? Ask Fedora pipewire , kde , kde-plasma , wayland , bluetooth , audio , intel , nvidia , server	16	517	September 10, 2024

Internet Latency Problems Fedora 41

Related topics