From: kernel <kernel@nea-fast.com>
To: netdev@oss.sgi.com
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.9 tcp problems
Date: Mon, 29 Nov 2004 13:03:34 -0500 [thread overview]
Message-ID: <41AB6476.8060405@nea-fast.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
I've run into a problem with 2.6.(8.1,9) after installing a secondary
firewall. When I try to pull data through the original firewall (mail,
http, ssh), it stops after approx. 260k. Running ethereal tells me "A
segment before the frame was lost" followed by a bunch of "This is a
TCP duplicate ack" when using ssh. All 2.4.x machines and windows
clients work fine. I built 2.4.28 and it works fine from my machine. I
also fiddled with tcp_ecn and that didn't fix it either. I don't have
any problems communicating to "local" machines. I've attached the
tcpdump output from an scp attempt. NIC is a 3Com Corporation 3c905B.
Thanks !
walt
[-- Attachment #2: dump.txt.gz --]
[-- Type: application/x-gzip, Size: 1165 bytes --]
next reply other threads:[~2004-11-29 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 18:03 kernel [this message]
2004-11-30 6:43 ` 2.6.9 tcp problems Willy Tarreau
2004-11-30 15:44 ` John Heffner
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=41AB6476.8060405@nea-fast.com \
--to=kernel@nea-fast.com \
--cc=linux-kernel@vger.kernel.org \
--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).