Bug 2448211 - ping -c10 fedoraproject.org returns 100% packet loss on Fedora KDE aarch64 Rpi4
Summary: ping -c10 fedoraproject.org returns 100% packet loss on Fedora KDE aarch64 Rpi4
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 44
Hardware: aarch64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-16 20:24 UTC by Derek Enz
Modified: 2026-03-26 17:11 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-03-26 17:11:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Derek Enz 2026-03-16 20:24:57 UTC
The issue does not seem to occur on x86 builds.

Bare metal Rpi 4 tests.

Reproducible: Always

Steps to Reproduce:
1.Install F44 KDE aarch64. Rpi 4 hardware.
2.Connect to network.
3.Open terminal and run ping -c10 fedoraproject.org
Actual Results:
Observe 100% packet loss

Expected Results:
Should be zero packet loss.

Additional Information:
Fedora 44 Branched 20260314 Build.

WIFI network.

Bare metal test on a Rpi 4.

Comment 1 Íñigo Huguet 2026-03-23 09:47:09 UTC
Please provide some information to see what might be happening. Provide the output of the following commands:

ip a
ip l
nmcli c
nmcli c show NAME_OF_THE_CONNECTION   <-- replace here with the name of the connection from the previous command
journalctl -b -k
journalctl -b -u NetworkManager

Comment 2 Derek Enz 2026-03-26 17:11:16 UTC
(In reply to Íñigo Huguet from comment #1)
> Please provide some information to see what might be happening. Provide the
> output of the following commands:
> 
> ip a
> ip l
> nmcli c
> nmcli c show NAME_OF_THE_CONNECTION   <-- replace here with the name of the
> connection from the previous command
> journalctl -b -k
> journalctl -b -u NetworkManager

Ok for the current build F44 Branched KDE 20260324 aarch64 it works for me.


Note You need to log in before you can comment on or make changes to this bug.