netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: gandalf@wlug.westbo.se (Martin Josefsson)
Cc: netdev@oss.sgi.com
Subject: Re: raw ipv6 broken in 2.4.19
Date: Tue, 13 Aug 2002 08:04:40 +0400 (MSD)	[thread overview]
Message-ID: <200208130404.IAA20030@sex.inr.ac.ru> (raw)
In-Reply-To: <1029186150.700.39.camel@tux> from "Martin Josefsson" at Aug 12, 2 11:02:29 pm

Hello!

> It seems to be the tulip driver,

Apparently, it corrupts IPv6 packets. I have seen this bug,
it was cured by tuning pci settings in bios setup to be more conservative.
The most intersting thing was that only ICMP IPv6 were corrupted. :-)

> attaching them, the tcpdump looked perfectly normal to me.

I do not think so, packets should have wrong checksum.

Alexey

  reply	other threads:[~2002-08-13  4:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-12 19:07 raw ipv6 broken in 2.4.19 Martin Josefsson
2002-08-12 19:20 ` kuznet
2002-08-12 21:02   ` Martin Josefsson
2002-08-13  4:04     ` kuznet [this message]
2002-08-13 11:32       ` Martin Josefsson
2002-08-13 13:30         ` kuznet
2002-08-13 13:47           ` Martin Josefsson
2002-08-13 13:58             ` kuznet
2002-08-13 17:14               ` Martin Josefsson
2002-08-13 20:06                 ` kuznet
2002-08-13 21:29                   ` Martin Josefsson
2002-08-13 22:13                     ` kuznet
2002-08-14 12:15                   ` Donald Becker
2002-08-14 13:13                     ` kuznet
2002-08-14  0:15                 ` Julian Anastasov
2002-08-13 22:00                   ` kuznet
2002-08-14  1:12                     ` Julian Anastasov
2002-08-13 22:18                       ` kuznet
2002-08-14  1:38                         ` Julian Anastasov
2002-08-13 23:02                           ` Martin Josefsson

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=200208130404.IAA20030@sex.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=gandalf@wlug.westbo.se \
    --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).