public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: 21442@gmx.net (Matjaz Omerzel)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bad TCP checksums - can you solve the puzzle?
Date: Wed, 22 Jan 2003 10:42:26 +0000 (GMT)	[thread overview]
Message-ID: <200301221042.h0MAgQjK000389@darkstar.example.net> (raw)
In-Reply-To: <3E2E6D84.8D485EF3@gmx.net> from "Matjaz Omerzel" at Jan 22, 2003 11:08:04 AM

> Network card is verified and working. IP checksums never fail (0 packets
> lost after two days of flood ping). TCP works with same kernel, same NIC
> but on a different machine (Athlon 950) as well as with same machine,
> same NIC and Windows 98. Needless to say, it works with different
> machine (PIII) and different OS (Win2k).
> 
> Machine is verified, it has been working reliably for years. If, instead
> of Tornado, I use a 3Com 3C509B (10Mbit EISA), the TCP works perfectly.
> But if Tornado card was defective, TCP should also work with Via Rhine
> (DFE-530TX) - but it DOESN'T. (However, drivers via-rhine and 3c59x I
> believe were made by the same author, just in case that makes any sense)

Is the bus speed of the 486, and the other machine you tested the
3x905C-TX in the same?  The 486 sounds like it has EISA and PCI busses
- are you sure that the PCI bus is set to the correct clock speed?

John.

      reply	other threads:[~2003-01-22 10:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22 10:08 Bad TCP checksums - can you solve the puzzle? Matjaz Omerzel
2003-01-22 10:42 ` John Bradford [this message]

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=200301221042.h0MAgQjK000389@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=21442@gmx.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