From: "David S. Miller" <davem@redhat.com>
To: mroos@linux.ee
Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: Linux TCP problem while talking to hostme.bkbits.net ?
Date: Mon, 12 Aug 2002 02:54:53 -0700 (PDT) [thread overview]
Message-ID: <20020812.025453.114975744.davem@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.43.0208121024250.29811-100000@romulus.cs.ut.ee>
From: Meelis Roos <mroos@linux.ee>
Date: Mon, 12 Aug 2002 10:28:10 +0300 (EEST)
Before and after the connetion attempt - looks like the number of bad
segments is increasing so probably not a TCP bug.
Since I can connect to this server fine from different locations, it
looks like something (ISP caches/shapers? cable modem?) is corrupting
specific packets in a reproducible way.
Aparently something is wrong with the checksums.
InErrs gets incremented in three cases:
1) Header too small, unlikely what you see
2) Bad SYN sequences, Abort On Syn in TcpExt would have been
incremented also if this were the case, it was not
3) Bad TCP checksum
Hmmm, do you have messages that say "hw tcp v4 csum failed"
in your kernel logs? Any other interesting kernel messages?
next prev parent reply other threads:[~2002-08-12 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 12:19 Linux TCP problem while talking to hostme.bkbits.net ? Meelis Roos
2002-08-11 21:25 ` kuznet
2002-08-12 7:28 ` Meelis Roos
2002-08-12 9:54 ` David S. Miller [this message]
2002-08-12 10:14 ` Meelis Roos
2002-08-12 17:32 ` kuznet
2002-08-13 8:40 ` Meelis Roos
2002-08-13 12:31 ` Roger Gammans
2002-09-19 13:15 ` Meelis Roos
2002-09-19 19:21 ` David S. Miller
2002-08-13 13:40 ` kuznet
2002-08-13 13:48 ` Larry McVoy
2002-08-13 13:57 ` Meelis Roos
[not found] <1029389331.20774.17.camel@lancelot>
2002-08-15 5:35 ` Clint Byrum
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=20020812.025453.114975744.davem@redhat.com \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.