| To: | netdev@xxxxxxxxxxx |
|---|---|
| Subject: | Re: IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 (in)compatible encryption methods |
| From: | Peter Bieringer <pb@xxxxxxxxxxxx> |
| Date: | Fri, 06 Jun 2003 08:25:47 +0200 |
| Cc: | usagi-users@xxxxxxxxxxxxxx |
| In-reply-to: | <20030605.215907.71090944.davem@redhat.com> |
| References: | <35410000.1054818456@klopffest.muc.aerasec.de> <20030605.215907.71090944.davem@redhat.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
--On Thursday, June 05, 2003 09:59:07 PM -0700 "David S. Miller"
<davem@xxxxxxxxxx> wrote:
> From: "Dr. Peter Bieringer" <pb@xxxxxxxxxxxx>
> 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 in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH][IPV6] keeping dst refcnt correctly with using xfrm, David S. Miller |
|---|---|
| Next by Date: | Re: [PATCH][IPV6] keeping dst refcnt correctly with using xfrm, Kazunori Miyazawa |
| Previous by Thread: | Re: IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 (in)compatible encryption methods, David S. Miller |
| Next by Thread: | RFC: Mechanism for adding MIPv6 extension headers, Henrik Petander |
| Indexes: | [Date] [Thread] [Top] [All Lists] |