From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: ipsec-tools-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [Ipsec-tools-devel] more phase 2 reinitiation problems
Date: Sun, 20 Mar 2005 15:06:54 +0100 [thread overview]
Message-ID: <423D837E.4040203@gmx.at> (raw)
In-Reply-To: <Pine.LNX.4.62.0503181523510.4403@bizon.gios.gov.pl>
Krzysztof Oledzki wrote:
> Please giva a try try the 2.6.12-rc1 kernel. I have just upgraded my
> system to this kernel and it seems that IPSec is able to survive first
> rekeying. Unfortunately only a first one - after a while (just before
> removing old expired keys) one of newly generated keys get removed and
> new traffic racoon generates two news keys. OK, it is _much_ better but
> still... not perfect.
Hi,
I have not got time to try 2.6.12-rc1 yet but kernel 2.6.11.5 with
ipsec-tools 0.3.3 works fine.
Bye,
Wilfried
prev parent reply other threads:[~2005-03-20 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42334B29.2080504@gmx.at>
2005-03-18 14:43 ` [Ipsec-tools-devel] more phase 2 reinitiation problems Krzysztof Oledzki
2005-03-20 14:06 ` Wilfried Weissmann [this message]
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=423D837E.4040203@gmx.at \
--to=wilfried.weissmann@gmx.at \
--cc=ipsec-tools-devel@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=olel@ans.pl \
/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).