From: Peter Bieringer <pb@bieringer.de>
To: netdev@oss.sgi.com
Cc: usagi-users@linux-ipv6.org
Subject: Re: IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 (in)compatible encryption methods
Date: Fri, 06 Jun 2003 08:25:47 +0200 [thread overview]
Message-ID: <122560000.1054880747@gate.muc.bieringer.de> (raw)
In-Reply-To: <20030605.215907.71090944.davem@redhat.com>
--On Thursday, June 05, 2003 09:59:07 PM -0700 "David S. Miller"
<davem@redhat.com> wrote:
> From: "Dr. Peter Bieringer" <pb@bieringer.de>
> Date: Thu, 05 Jun 2003 15:07:36 +0200
>
> because I got no success, I've tried different encryption methods than
> 3DES. And *suddenly* it began to work.
>
> Sounds like an out-of-date include/linux/pfkeyv2.h file
> used during tool building.
Yes, it looks like.
BTW: is there something like a "version information" which is used in that
way that user space tools can detect and report such changes at runtime?
Would be perhaps helpful if racoon reports something like "incompatible" in
this case. Very much better than such strange problems...
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
prev parent reply other threads:[~2003-06-06 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 13:07 (usagi-users 02412) IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 (in)compatible encryption methods Dr. Peter Bieringer
2003-06-05 14:16 ` James Morris
2003-06-05 14:20 ` (usagi-users 02412) IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 Dr. Peter Bieringer
2003-06-05 14:25 ` James Morris
2003-06-05 14:20 ` (usagi-users 02415) IPsec 2.5.70-bk9 and Check Point VPN-1 NG FP4 RC Dr. Peter Bieringer
2003-06-06 4:59 ` IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 (in)compatible encryption methods David S. Miller
2003-06-06 6:25 ` Peter Bieringer [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=122560000.1054880747@gate.muc.bieringer.de \
--to=pb@bieringer.de \
--cc=netdev@oss.sgi.com \
--cc=usagi-users@linux-ipv6.org \
/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).