From: Michal Vanco <vanco@satro.sk>
To: netdev@oss.sgi.com
Subject: Re: e1000 packet corruption problem
Date: Wed, 06 Apr 2005 16:27:17 +0200 [thread overview]
Message-ID: <4253F1C5.2090203@satro.sk> (raw)
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
Hello,
I've made some more testing. This one was pretty surprising:
>From 192.168.0.2:
# sudo ping 192.168.0.1 -p fefffefffefffeff -i 0.01 -c 100
100 packets transmitted, 100 received, 0% packet loss, time 901ms
# sudo ping 192.168.0.1 -p fffefffefffefffe -i 0.01 -c 100
100 packets transmitted, 18 received, 82% packet loss, time 1068ms
Any ideas of how to solve this?
regards,
michal
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2005-04-06 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 14:27 Michal Vanco [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-29 16:02 e1000 packet corruption problem Brandeburg, Jesse
2005-03-29 15:42 ` Michal Vanco
2005-03-30 7:04 ` Michal Vanco
2005-03-29 8:55 Michal Vanco
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=4253F1C5.2090203@satro.sk \
--to=vanco@satro.sk \
--cc=netdev@oss.sgi.com \
/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).