From: Richard A Nelson <cowboy@vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test2-mm1 & ipsec-tools (xfrm_type_2_50?)
Date: Wed, 30 Jul 2003 16:22:25 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0307301515250.26621@onqynaqf.yrkvatgba.voz.pbz> (raw)
I built ipsec-tools against the 2.6.0-test2-mm1 includes and am *so*
close to getting it to work...
I'm getting odd errors from racoon:
INFO: isakmp.c:797:isakmp_ph1begin_i(): initiate new phase 1
negotiation: 9.30.62.131[500]<=>9.51.94.26[500]
INFO: isakmp.c:802:isakmp_ph1begin_i(): begin Identity Protection mode.
INFO: isakmp.c:2418:log_ph1established(): ISAKMP-SA established
9.30.62.131[500]-9.51.94.26[500] spi:36dbc14ce81d5d28:dc42216efd6549d4
INFO: isakmp.c:941:isakmp_ph2begin_i(): initiate new phase 2 negotiation:
9.30.62.131[0]<=>9.51.94.26[0]
modprobe: FATAL: Module ripemd160 not found.
modprobe: FATAL: Module cast128 not found.
modprobe: FATAL: Module lzs not found.
modprobe: FATAL: Module lzjh not found.
modprobe: FATAL: Module xfrm_type_2_50 not found.
modprobe: FATAL: Module ripemd160 not found.
modprobe: FATAL: Module cast128 not found.
modprobe: FATAL: Module lzs not found.
modprobe: FATAL: Module lzjh not found.
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 ?
--
Rick Nelson
I can saw a woman in two, but you won't want to look in the box when I do
'For My Next Trick I'll Need a Volunteer' -- Warren Zevon
next reply other threads:[~2003-07-30 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 20:22 Richard A Nelson [this message]
2003-07-30 21:04 ` 2.6.0-test2-mm1 & ipsec-tools (xfrm_type_2_50?) bert hubert
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=Pine.LNX.4.56.0307301515250.26621@onqynaqf.yrkvatgba.voz.pbz \
--to=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 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).