Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1308890

Summary: ping with count 1 doesn't work in rhel 7 while it works with count 2
Product: Red Hat Enterprise Linux 7 Reporter: Abhi <abhisheksingh538>
Component: iputilsAssignee: Jan Synacek <jsynacek>
Status: CLOSED CURRENTRELEASE QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.2CC: jsynacek, todoleza
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-21 11:43:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1400961    

Description Abhi 2016-02-16 11:16:35 UTC
iputils version :  20121221-7.el7

I have a simulator which simulates physical devices on a remote network, each of these virtual devices have different ips, when i try to ping one of these devices, from RHEL7 using the command

   "ping -c 1 172.20.1.xxx"

the output i get :

PING 172.20.1.xxx (172.20.1.xx) 56(84) bytes of data.
From 10.3.1.xyz: icmp_seq=1 Redirect Network(New nexthop: 10.3.1.yy)
From 10.3.1.xyz icmp_seq=1 Redirect Network
--- 172.20.1.xxx ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

while when using the following command:

"ping -c 2 172.20.1.xxx"

the output i get:

PING 172.20.1.xxx (172.20.1.xxx) 56(84) bytes of data.
From 10.3.1.xyz: icmp_seq=1 Redirect Network(New nexthop: 10.3.1.yy)
From 10.3.1.xyz icmp_seq=1 Redirect Network64 bytes from 172.20.1.xxx:    
icmp_seq=1 ttl=63 time=59.1 ms

--- 172.20.1.xxx ping statistics ---
1 packets transmitted, 1 received, +1 errors, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 59.144/59.144/59.144/0.000 ms

This as i can see involves redirection of network from one ip to other. But using the command :

"ping -c 1 172.20.1.xxx"

works fine in RHEL6, with the output as:

PING 172.20.1.xxx (172.20.1.xxx) 56(84) bytes of data.
From 10.3.1.xyz: icmp_seq=1 Redirect Network(New nexthop: 10.3.1.yy)
64 bytes from 172.20.1.xxx: icmp_seq=1 ttl=63 time=58.9 ms

--- 172.20.1.xxx ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 58ms
rtt min/avg/max/mdev = 58.931/58.931/58.931/0.000 ms

Why is the ping behavior different in RHEL7?

Comment 2 Jan Synacek 2016-03-01 09:54:15 UTC
(In reply to Abhi from comment #0)
> Why is the ping behavior different in RHEL7?

Because the versions are ages apart. Moreover, iputils might be rebased in RHEL-7.3, see bz#1273336.


Packages for i386 are not supported. This bug report is not a valid bug report. You should contact the Red Hat support.

Comment 3 Abhi 2016-03-04 09:23:03 UTC
(In reply to Jan Synacek from comment #2)
> (In reply to Abhi from comment #0)
> > Why is the ping behavior different in RHEL7?
> 
> Because the versions are ages apart. Moreover, iputils might be rebased in
> RHEL-7.3, see bz#1273336.
> 
> 
> Packages for i386 are not supported. This bug report is not a valid bug
> report. You should contact the Red Hat support.

I beg your pardon, but by mistake i mentioned the hardware architecture as i386 instead of "x86_64".
Can you please look into the issue considering hardware architecture as "x86_64 Linux".

The iputils version using which i am facing issues is of version:
iputils.x86_64               20121221-7.el7    @anaconda/7.2

While everyting works fine with RHEL 6.4 which has iputils as:
iputils.x86_64             20071127-16.el6

I am changing the status of bug from closed to New.

-Thanks

Comment 4 Jan Synacek 2017-02-21 11:43:32 UTC
Works for me in iputils-20160308-8.el7.x86_64