From: bert hubert <ahu@ds9a.nl>
To: Richard A Nelson <cowboy@vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-mm1 & ipsec-tools (xfrm_type_2_50?)
Date: Wed, 30 Jul 2003 23:04:14 +0200 [thread overview]
Message-ID: <20030730210414.GA28308@outpost.ds9a.nl> (raw)
In-Reply-To: <Pine.LNX.4.56.0307301515250.26621@onqynaqf.yrkvatgba.voz.pbz>
On Wed, Jul 30, 2003 at 04:22:25PM -0400, Richard A Nelson wrote:
>
> I built ipsec-tools against the 2.6.0-test2-mm1 includes and am *so*
> close to getting it to work...
I recently tested all this again with 2.6.0-test2 and It Just Worked, so I
can't confirm this.
> modprobe: FATAL: Module xfrm_type_2_50 not found.
> ERROR: pfkey.c:209:pfkey_handler(): pfkey UPDATE failed:
> No buffer space available
> ERROR: pfkey.c:209:pfkey_handler(): pfkey ADD failed: No buffer space available
>
> all the ipsec and crypto stuff is modular, for the nonce, until I figure
> what I need/want.
>
> most of the module not found messages are fine, its xfrm_type_2_50 that
> I'm worried about... What am I missing ?
I run with a very minimal racoon.conf, almost exactly the one found on
http://lartc.org/howto/lartc.ipsec.html
I'd suggest posting the relevant bits of your .config
Good luck!
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2003-07-30 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 20:22 2.6.0-test2-mm1 & ipsec-tools (xfrm_type_2_50?) Richard A Nelson
2003-07-30 21:04 ` bert hubert [this message]
2003-07-30 21:24 ` Richard A Nelson
2003-07-30 21:42 ` Jose Luis Domingo Lopez
2003-07-30 22:22 ` Richard A Nelson
2003-07-31 0:00 ` James Morris
2003-07-31 0:27 ` Richard A Nelson
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=20030730210414.GA28308@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=cowboy@vnet.ibm.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.