Bug 26650 - ping only returns one line
Summary: ping only returns one line
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: iputils   
(Show other bugs)
Version: 6.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Aaron Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2001-02-08 03:44 UTC by Ravindran Karupiah
Modified: 2015-03-05 01:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-17 15:08:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ravindran Karupiah 2001-02-08 03:44:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

ping only returns one line until Ctrl-C

Reproducible: Always
Steps to Reproduce:
1.run ping

Actual Results:  apollo# ping localhost
PING localhost ( from : 56(84) bytes of data.
64 bytes from localhost ( icmp_seq=0 ttl=255 time=0.3 ms
--- localhost ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.3/0.3/0.3 ms

Comment 1 Pekka Savola 2001-02-12 21:38:03 UTC
1. which version of ping?  If not the errata, try updating.
2. does this happen with non-localhost too?  
3. ping -n is bad too? 
4. you haven't tweaked /proc/sys/net/ipv4/icmp_echo* ?
5. what does 'tcpdump -n icmp' say ?

Comment 2 Ravindran Karupiah 2001-02-13 01:05:02 UTC
1. which version of ping?  If not the errata, try updating.
       >> iputils-ss990107 and have updated but problem still there.

2. does this happen with non-localhost too?
       >> yes
3. ping -n is bad too? 
       >> yes, same

4. you haven't tweaked /proc/sys/net/ipv4/icmp_echo* ?
       >> no

5. what does 'tcpdump -n icmp' say ?
       >> when ping is executed only the following appears.

# tcpdump -n icmp
Kernel filter, protocol ALL, datagram packet socket
tcpdump: listening on all devices
16:04:37.475973   lo > > icmp: echo request
16:04:37.475973   lo < > icmp: echo request
16:04:37.476058   lo > > icmp: echo reply
16:04:37.476058   lo < > icmp: echo reply

Comment 3 Curtis Doty 2001-05-15 01:57:49 UTC
Had same problem with netkit-base-0.10-37 and upgraded to iputils-20001110-1 
where I now get the error with a warning: no SO_TIMESTAMP support, falling back 
to SIOCGSTAMP. Are they connected? Kernel is 2.2. tcpdump icmp shows only one 
echo request and its reply no matter what I do with -c and -w.

Comment 4 Phil Knirsch 2001-06-26 12:33:20 UTC
Could you offer some more info, maybe of the hardware you are using?

I remember some strange things happening with older 486 boards, maybe it could
be some kind of hardware problem where timers don't work correctly.

Otherwise i'd recommend to upgrade the system to 7.1 and see if the problem
still occurs. The new kernel and new iptutils package might solve it.

Read ya, Phil

Comment 5 Pekka Savola 2001-07-17 15:07:57 UTC
I happened to come across this:


List:     linux-kernel
Subject:  alarm() does not work/ping only sends one packet on SMP machine (2.2.16)
From:     Tobias Haustein <tobias.haustein@aixigo.de>
Date:     2001-07-17 12:02:07

Might be related; the behaviour at least seems vaguely familiar.

Comment 6 Phil Knirsch 2002-03-12 13:34:22 UTC
As i can't reproduce this bug and as it looks like it might be a kernel problem
i am closing this bug as 'WORKSFORME' now.

Please try with latest kernel/glibc and iputils (I've tried various setups with
kernel 2.2 and 2.4).

Read ya, Phil

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