Bug 2384212 - ping -c1 no longer works
Summary: ping -c1 no longer works
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: iputils
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2386883 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-29 07:58 UTC by Didier
Modified: 2025-08-22 02:11 UTC (History)
4 users (show)

Fixed In Version: iputils-20250605-1.fc43 iputils-20250605-1.fc42 iputils-20250605-1.fc41
Clone Of:
Environment:
Last Closed: 2025-08-07 05:58:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Didier 2025-07-29 07:58:58 UTC
ping -c1 no longer works

https://github.com/iputils/iputils/issues/596

Reproducible: Always

Steps to Reproduce:
1.`ping google.com -c1`


Actual Results:
100% packet loss

Expected Results:
0% packet loss

Comment 1 Max Chernoff 2025-07-30 07:16:12 UTC
I am also experiencing this bug; specifically, this is a regression from `iputils-0:20240905-4.fc42.x86_64` to `iputils-0:20250602-3.fc42.x86_64`.

Shell transcript from before the update:

    $ ping -V
    ping from iputils 20240905
    libcap: yes, IDN: yes, NLS: yes, error.h: yes, getrandom(): yes, __fpending(): yes
    
    $ rpm --query --queryformat='%{NAME}\t%{VERSION}\n' iputils
    iputils	20240905
    
    $ ping -c 1 fedoraproject.org
    PING fedoraproject.org (2604:1580:fe00:0:dead:beef:cafe:fed1) 56 data bytes
    64 bytes from 2604:1580:fe00:0:dead:beef:cafe:fed1: icmp_seq=1 ttl=53 time=69.0 ms
    
    --- fedoraproject.org ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 68.999/68.999/68.999/0.000 ms
    
    $ ping -c 2 fedoraproject.org
    PING fedoraproject.org (2604:1580:fe00:0:dead:beef:cafe:fed1) 56 data bytes
    64 bytes from 2604:1580:fe00:0:dead:beef:cafe:fed1: icmp_seq=1 ttl=53 time=68.5 ms
    64 bytes from 2604:1580:fe00:0:dead:beef:cafe:fed1: icmp_seq=2 ttl=53 time=63.0 ms
    
    --- fedoraproject.org ping statistics ---
    2 packets transmitted, 2 received, 0% packet loss, time 1002ms
    rtt min/avg/max/mdev = 63.011/65.737/68.463/2.726 ms

And from after the update:

    $ ping -V
    ping from iputils 20250602
    libcap: yes, IDN: yes, NLS: yes, error.h: yes, getrandom(): yes, __fpending(): yes
    
    $ rpm --query --queryformat='%{NAME}\t%{VERSION}\n' iputils
    iputils	20250602
    
    $ ping -c 1 fedoraproject.org
    PING fedoraproject.org (2604:1580:fe00:0:dead:beef:cafe:fed1) 56 data bytes
    
    --- fedoraproject.org ping statistics ---
    1 packets transmitted, 0 received, 100% packet loss, time 0ms
    
    $ ping -c 2 fedoraproject.org
    PING fedoraproject.org (2604:1580:fe00:0:dead:beef:cafe:fed1) 56 data bytes
    64 bytes from 2604:1580:fe00:0:dead:beef:cafe:fed1: icmp_seq=1 ttl=53 time=67.7 ms
    64 bytes from 2604:1580:fe00:0:dead:beef:cafe:fed1: icmp_seq=2 ttl=53 time=60.5 ms
    
    --- fedoraproject.org ping statistics ---
    2 packets transmitted, 2 received, 0% packet loss, time 1001ms
    rtt min/avg/max/mdev = 60.545/64.139/67.734/3.594 ms

Comment 2 Rajeesh 2025-08-06 09:26:17 UTC
I spent a few days trying to troubleshoot a supplier script which was using `ping -c1` to check if a server was up; and finally found the update that broke it. Upstream promptly fixed it and released https://github.com/iputils/iputils/releases/tag/20250605, please update Fedora package as early as possible.

Comment 3 Kevin Fenzi 2025-08-06 16:14:39 UTC
*** Bug 2386883 has been marked as a duplicate of this bug. ***

Comment 4 Kevin Fenzi 2025-08-06 18:24:17 UTC
Sorry for the delay here. Will look at pushing updates today hopefully.

Comment 5 Fedora Update System 2025-08-06 18:35:11 UTC
FEDORA-2025-da10aac783 (iputils-20250605-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-da10aac783

Comment 6 Fedora Update System 2025-08-06 18:45:23 UTC
FEDORA-2025-7780629e7b (iputils-20250605-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-7780629e7b

Comment 7 Fedora Update System 2025-08-06 18:45:23 UTC
FEDORA-2025-b88542a0da (iputils-20250605-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-b88542a0da

Comment 8 Fedora Update System 2025-08-07 01:30:50 UTC
FEDORA-2025-7780629e7b has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-7780629e7b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7780629e7b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2025-08-07 02:11:03 UTC
FEDORA-2025-b88542a0da has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-b88542a0da`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-b88542a0da

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2025-08-07 05:58:16 UTC
FEDORA-2025-da10aac783 (iputils-20250605-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2025-08-08 00:54:31 UTC
FEDORA-2025-7780629e7b (iputils-20250605-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2025-08-22 02:11:28 UTC
FEDORA-2025-b88542a0da (iputils-20250605-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


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