From: bert hubert <ahu@ds9a.nl>
To: Andreas Jellinghaus <aj@dungeon.inka.de>
Cc: mit_warlord@users.sourceforge.net, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: ipsec-tools 0.1 + kernel 2.5.64
Date: Wed, 5 Mar 2003 12:28:52 +0100 [thread overview]
Message-ID: <20030305112852.GA22351@outpost.ds9a.nl> (raw)
In-Reply-To: <1046863752.441.7.camel@simulacron>
On Wed, Mar 05, 2003 at 12:29:12PM +0100, Andreas Jellinghaus wrote:
> Hi,
>
> both manual keying and automatic keying with racoon (pre-shared secret)
> are working fine. No need to patch or modify anything.
> I tried only ipv4.
By the way, regarding ipsec-tools 0.1, are you sure you want to fork the
projects involved?
By the way, you did not mention it here but ipsec-tools is available on
http://sourceforge.net/projects/ipsec-tools , I also link them from
http://lartc.org/howto/lartc.ipsec.html
Regards,
bert
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
http://netherlabs.nl Consulting
next parent reply other threads:[~2003-03-05 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1046863752.441.7.camel@simulacron>
2003-03-05 11:28 ` bert hubert [this message]
2003-03-05 14:52 ` ipsec-tools 0.1 + kernel 2.5.64 Derek Atkins
2003-03-05 21:28 ` Andreas Jellinghaus
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=20030305112852.GA22351@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=aj@dungeon.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mit_warlord@users.sourceforge.net \
--cc=netdev@oss.sgi.com \
/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).