From: "José Luis Domingo López" <jldomingo@crosswinds.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.2.19 -> 80% Packet Loss
Date: Fri, 15 Jun 2001 01:14:16 +0000 [thread overview]
Message-ID: <20010615011415.A5210@dardhal.mired.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0106141325210.20189-100000@localhost.localdomain>
On Thursday, 14 June 2001, at 14:17:11 -0700,
chuckw@altaserv.net wrote:
>
> 1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
> packet loss when doing a ping -f with a packet size of 64590 or higher.
>
What happens here is (under kernel 2.2.19):
ping -f -s 49092 localhost -->> 0 % packet loss
ping -f -s 49093 localhost -->> 100 % packet loss
Maybe this has something to do with fragmentation of IP packets to fit in
the underlying protocol's MTU (3929 in my loopback device).
When pinging from the network, it is expected to get an increasing number
of lost packets due to collisions in the medium. Moreover, IP
fragmentation, encapsulation and reassembly can be a reason for lost
packets, but is clear that what you get is quite strange :)
What I have noticed is that pinging from the network with large packet
sizes (for example, ping -s 55000 destinationIP), causes the ping program
to sometimes dump a echo_reply packet to stdout with the following message:
55008 bytes from 192.168.1.10: icmp_seq=8 ttl=255 time=145.9 ms
wrong data byte #190 should be 0xbe but was 0x3e
And some other times I get ping results with interesting patterns:
55008 bytes from 192.168.1.10: icmp_seq=45 ttl=255 time=1155.6 ms
55008 bytes from 192.168.1.10: icmp_seq=46 ttl=255 time=143.3 ms
55008 bytes from 192.168.1.10: icmp_seq=47 ttl=255 time=1155.2 ms
55008 bytes from 192.168.1.10: icmp_seq=48 ttl=255 time=143.8 ms
On a slower box, I get the following (kernel 2.4.4):
ping -f -s 32293 localhost -->> 0 % packet loss
ping -f -s 32294 localhost -->> 100 % packet loss
I've no idea what this could mean.
--
José Luis Domingo López
Linux Registered User #189436 Debian GNU/Linux Potato (P166 64 MB RAM)
jdomingo EN internautas PUNTO org => ¿ Spam ? Atente a las consecuencias
jdomingo AT internautas DOT org => Spam at your own risk
next prev parent reply other threads:[~2001-06-14 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 21:17 [BUG] 2.2.19 -> 80% Packet Loss chuckw
2001-06-14 23:44 ` Scott Laird
2001-06-15 14:17 ` chuckw
2001-06-15 17:56 ` Scott Laird
2001-06-15 1:14 ` José Luis Domingo López [this message]
2001-06-15 9:12 ` Tim Moore
2001-06-15 9:10 ` Tim Moore
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=20010615011415.A5210@dardhal.mired.net \
--to=jldomingo@crosswinds.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).