From: Tim Moore <timothymoore@bigfoot.com>
To: linux-kernel@vger.kernel.org
Cc: "José Luis Domingo López" <jldomingo@crosswinds.net>
Subject: Re: [BUG] 2.2.19 -> 80% Packet Loss
Date: Fri, 15 Jun 2001 02:12:59 -0700 [thread overview]
Message-ID: <3B29D19B.48A62E4B@bigfoot.com> (raw)
In-Reply-To: <20010615011415.A5210@dardhal.mired.net>
José Luis Domingo López wrote:
>
> 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
[tim@abit cron.daily]# ping -w 10 -f -s 49093 localhost
PING localhost (127.0.0.1) from 127.0.0.1 : 49093(49121) bytes of data.
Warning: no SO_RCVTIMEO support, falling back to poll
.
--- localhost ping statistics ---
8051 packets transmitted, 8051 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.517/0.751/25.336/0.678 ms
> Maybe this has something to do with fragmentation of IP packets to fit in
> the underlying protocol's MTU (3929 in my loopback device).
[tim@abit cron.daily]# ifconfig lo
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:1197462 errors:0 dropped:0 overruns:0 frame:0
TX packets:1197462 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
[tim@abit cron.daily]# cat /proc/version
Linux version 2.2.20p2-ai (root@abit) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #12 Fri May 25 16:31:02 PDT 2001
--
next prev parent reply other threads:[~2001-06-15 9: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
2001-06-15 9:12 ` Tim Moore [this message]
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=3B29D19B.48A62E4B@bigfoot.com \
--to=timothymoore@bigfoot.com \
--cc=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