From: Willy Tarreau <willy@w.ods.org>
To: kernel <kernel@nea-fast.com>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 tcp problems
Date: Tue, 30 Nov 2004 07:43:38 +0100 [thread overview]
Message-ID: <20041130064338.GI783@alpha.home.local> (raw)
In-Reply-To: <41AB6476.8060405@nea-fast.com>
It is possible that the autoneg code has changed between 2.4 and 2.6
for the interface connected to the current firewall, and that you lose
packets because of a duplex mismatch. Please check the negociation
with ethtool on your system, and do so on the other firewall.
Regards,
willy
On Mon, Nov 29, 2004 at 01:03:34PM -0500, kernel wrote:
> 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
>
next prev parent reply other threads:[~2004-11-30 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 18:03 2.6.9 tcp problems kernel
2004-11-29 18:35 ` Stephen Hemminger
2004-11-30 6:43 ` Willy Tarreau [this message]
2004-11-30 15:44 ` John Heffner
-- strict thread matches above, loose matches on Subject: below --
2004-11-29 19:44 kernel
2004-12-01 14:11 ` Mark Watts
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=20041130064338.GI783@alpha.home.local \
--to=willy@w.ods.org \
--cc=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