From: Sean Neakums <sneakums@zork.net>
To: James Morris <jmorris@intercode.com.au>
Cc: netdev@oss.sgi.com, <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.0-test1-mm1] TCP connections over ipsec hang after a few seconds
Date: Sun, 20 Jul 2003 13:29:24 +0100 [thread overview]
Message-ID: <6u8yqt8jq3.fsf@zork.zork.net> (raw)
In-Reply-To: <Mutt.LNX.4.44.0307201552580.22965-100000@excalibur.intercode.com.au> (James Morris's message of "Sun, 20 Jul 2003 15:58:13 +1000 (EST)")
James Morris <jmorris@intercode.com.au> writes:
> On Sat, 19 Jul 2003, Sean Neakums wrote:
>
>> twenty. The problem seems unrelated to the amount of data
>> transferred; I've tried both bulk rsync transfers and ssh sessions.
>> I've also tested the same boxes over 100baseT; still happens.
>
> It sounds a bit like a pmtu problem related to the wireless bridge, but
> that would be dependent on amount of data transferred and should not
> happen on 100baseT.
I am seeing a lot of "pmtu discvovery on SA AH/03537192/c0a80003" type
messages (I forgot to check for them when on 100baseT; will recheck
that). Are these indicative of such a problem? I seem to recall that
reducing the max MTU is not as straightforward as just adjusting the
interfaces' mtu setting. What should I do to eliminate pmtu as the
source of the problem?
> Transport mode (just blowfish encryption) looks to be working ok for me,
> I'm able to ftp uncompressed kernel tarballs between two boxes over
> gigabit ethernet with no apparent problems.
I had been using 3des with AH; just retried with blowfish 448 and no
AH with much the same result.
next prev parent reply other threads:[~2003-07-20 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 13:40 [2.6.0-test1-mm1] TCP connections over ipsec hang after a few seconds Sean Neakums
2003-07-20 5:58 ` James Morris
2003-07-20 12:29 ` Sean Neakums [this message]
2003-07-20 15:21 ` James Morris
2003-07-20 19:23 ` Sean Neakums
2003-07-20 19:47 ` Sean Neakums
2003-07-21 0:28 ` James Morris
2003-07-21 0:37 ` Sean Neakums
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=6u8yqt8jq3.fsf@zork.zork.net \
--to=sneakums@zork.net \
--cc=jmorris@intercode.com.au \
--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).