From: Patrick McHardy <kaber@trash.net>
To: Steve Hill <steve@services.navaho.net>
Cc: netdev@oss.sgi.com
Subject: Re: More IPSEC trouble
Date: Thu, 10 Mar 2005 18:15:54 +0100 [thread overview]
Message-ID: <423080CA.3060604@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0503101229380.18067@sorbus2.navaho>
Steve Hill wrote:
>
> Unfortunately I've found another IPSEC kernel bug (2.6.10):
>
> Increasing the packet size by 1 byte would obviously require
> fragmentation of the encrypted packet and causes the machine to lock up.
Doesn't sound familiar to me, but I would recommend trying
2.6.11 anyway.
Regards
Patrick
next prev parent reply other threads:[~2005-03-10 17:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 12:45 More IPSEC trouble Steve Hill
2005-03-10 15:01 ` Nicolas DICHTEL
2005-03-10 16:32 ` Steve Hill
2005-03-10 17:15 ` Patrick McHardy [this message]
2005-03-11 1:17 ` Herbert Xu
2005-03-11 15:05 ` Steve Hill
2005-03-12 0:00 ` Patrick McHardy
2005-03-12 0:11 ` Patrick McHardy
2005-03-12 0:13 ` Patrick McHardy
2005-03-12 1:35 ` Herbert Xu
2005-03-12 2:35 ` Patrick McHardy
2005-03-14 12:12 ` Steve Hill
2005-03-15 5:39 ` David S. Miller
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=423080CA.3060604@trash.net \
--to=kaber@trash.net \
--cc=netdev@oss.sgi.com \
--cc=steve@services.navaho.net \
/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).