From: Richard A Nelson <cowboy@vnet.ibm.com>
To: bert hubert <ahu@ds9a.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-mm1 & ipsec-tools (xfrm_type_2_50?)
Date: Wed, 30 Jul 2003 17:24:36 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0307301710550.26621@onqynaqf.yrkvatgba.voz.pbz> (raw)
In-Reply-To: <20030730210414.GA28308@outpost.ds9a.nl>
On Wed, 30 Jul 2003, bert hubert wrote:
> I recently tested all this again with 2.6.0-test2 and It Just Worked, so I
> can't confirm this.
with an all modular build ?
> I run with a very minimal racoon.conf, almost exactly the one found on
> http://lartc.org/howto/lartc.ipsec.html
ditto
> I'd suggest posting the relevant bits of your .config
!/usr/sbin/setkey -f
flush;
spdflush;
spdadd 9.30.62.131 9.51.94.26 any -P out ipsec
esp/transport//require;
spdadd 9.51.94.26 9.30.62.131 any -P in ipsec
esp/transport//require;
/etc/racoon/racoon.conf
remote 9.51.94.26
{
exchange_mode main;
my_identifier asn1dn;
peers_identifier asn1dn;
certificate_type x509 "<cert>" "<key>";
peers_certfile "<remote cert>";
proposal {
encryption_algorithm 3des;
hash_algorithm sha1;
authentication_method rsasig;
dh_group modp1536 ;
}
}
sainfo anonymous
{
pfs_group modp1536;
encryption_algorithm 3des ;
authentication_algorithm hmac_sha1 ;
compression_algorithm deflate ;
}
Again, the remote is freeswan 1.96
> Good luck!
Thanks, I'll probably be needing it :)
--
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 prev parent reply other threads:[~2003-07-30 21:27 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
2003-07-30 21:24 ` Richard A Nelson [this message]
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.0307301710550.26621@onqynaqf.yrkvatgba.voz.pbz \
--to=cowboy@vnet.ibm.com \
--cc=ahu@ds9a.nl \
--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).