From: Rinto Exandy <mysuse@gmail.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: icmp gaps
Date: Thu, 26 Aug 2004 11:35:57 +0700 [thread overview]
Message-ID: <e892b9d1040825213577b6e376@mail.gmail.com> (raw)
In-Reply-To: <a0f69e504082521196c31a01a@mail.gmail.com>
On Thu, 26 Aug 2004 09:19:16 +0500, Askar <askarali@gmail.com> wrote:
> hi all
>
> Below is the output of ping to our billing server from on one of
> another server, when one look into "icmp_seq" sometime there is gap
> between two packets for example in icmp_seq=25 <---> icmp_seq=28 and
> icmp_seq=21 <---> icmp_seq=23.
Theese gaps means that the packet is "time out", if you use Win32
you'll see "Request Time Out" at icmp_seq 26,27 and 22. Is this
something to worry about ?? Yes ofcourse, many gaps means many request
time out ( the packet didn't reach the destionation in a manner or
time). You need to check the network.
/* sorry my english is bad :) */
> I just wants to know these gaps are normal or something to worried about?
>
> regards
> Askar
>
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=0 ttl=61 time=6.65 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=2 ttl=61 time=22.5 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=3 ttl=61 time=9.77 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=4 ttl=61 time=26.9 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=5 ttl=61 time=22.6 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=8 ttl=61 time=13.1 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=9 ttl=61 time=40.4 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=10 ttl=61 time=24.0 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=11 ttl=61 time=18.9 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=12 ttl=61 time=5.80 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=13 ttl=61 time=26.1 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=14 ttl=61 time=26.6 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=15 ttl=61 time=16.9 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=16 ttl=61 time=7.64 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=17 ttl=61 time=8.67 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=18 ttl=61 time=8.04 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=19 ttl=61 time=5.86 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=21 ttl=61 time=6.14 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=23 ttl=61 time=5.82 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=24 ttl=61 time=5.84 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=25 ttl=61 time=11.1 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=28 ttl=61 time=5.89 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=29 ttl=61 time=5.81 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=30 ttl=61 time=5.79 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=31 ttl=61 time=13.3 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=32 ttl=61 time=5.79 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=33 ttl=61 time=8.52 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=35 ttl=61 time=25.1 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=36 ttl=61 time=8.17 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=38 ttl=61 time=5.97 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=39 ttl=61 time=6.04 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=40 ttl=61 time=13.4 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=41 ttl=61 time=29.1 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=42 ttl=61 time=26.0 ms
> 64 bytes from ab.abc.net (xxx.xxxx.xx.xx): icmp_seq=43 ttl=61 time=12.9 ms
> --
> "If you really want something in this life, you have to work for it.
> Now, quiet! They're about to announce the lottery numbers..."
> - Homer Simpson
>
>
next prev parent reply other threads:[~2004-08-26 4:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 4:19 icmp gaps Askar
2004-08-26 4:35 ` Rinto Exandy [this message]
2004-08-26 11:07 ` Deepak Seshadri
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=e892b9d1040825213577b6e376@mail.gmail.com \
--to=mysuse@gmail.com \
--cc=netfilter@lists.netfilter.org \
/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