From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: "Ole Bj�rn Hessen" <obh@telenor.net>
Cc: netdev@vger.kernel.org, YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH iputils ping]: report outstanding packets before sending next packet
Date: Tue, 10 Jan 2012 00:20:43 +0900 [thread overview]
Message-ID: <4F0B05CB.1080803@linux-ipv6.org> (raw)
In-Reply-To: <201201050904.KAA04877@shell02.nsc.no>
Ole Bj�rn Hessen wrote:
> Hello,
>
> please accept following patch to ping to let ping report outstanding
> packets before sending next packet. This is a sorely missed feature
> from the old sun ping. Very useful together with the -D option:
>
> ping -DO 10.122.145.180> file
> # wait next day
> ^C
> grep "no answer yet" file
>
> [1325752664.026900] 64 bytes from 10.122.145.180: icmp_req=20 ttl=64 time=0.695 ms
> [1325752665.026926] 64 bytes from 10.122.145.180: icmp_req=21 ttl=64 time=0.695 ms
> [1325752666.026917] 64 bytes from 10.122.145.180: icmp_req=22 ttl=64 time=0.682 ms
> [1325752667.026922] 64 bytes from 10.122.145.180: icmp_req=23 ttl=64 time=0.695 ms
> [1325752669.026217] no answer yet for icmp_seq=24
> [1325752670.026207] no answer yet for icmp_seq=25
> ...
> [1325752697.026206] no answer yet for icmp_seq=52
> [1325752698.026205] no answer yet for icmp_seq=53
> [1325752698.026962] 64 bytes from 10.122.145.180: icmp_req=54 ttl=64 time=0.717 ms
> [1325752699.026930] 64 bytes from 10.122.145.180: icmp_req=55 ttl=64 time=0.690 ms
> [1325752700.026928] 64 bytes from 10.122.145.180: icmp_req=56 ttl=64 time=0.695 ms
>
> Kind regards,
>
> Ole Bjørn Hessen,
> Telenor
Applied, thanks.
Please provide the "signed-off-by" line, next time.
--yoshfuji
next parent reply other threads:[~2012-01-09 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201201050904.KAA04877@shell02.nsc.no>
2012-01-09 15:20 ` YOSHIFUJI Hideaki [this message]
2012-01-05 9:04 [PATCH iputils ping]: report outstanding packets before sending next packet Ole Bjorn Hessen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0B05CB.1080803@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=netdev@vger.kernel.org \
--cc=obh@telenor.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).