From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] more than 1 Line - but not with FreeS/WAN
Date: Mon, 03 Dec 2001 23:24:58 +0000 [thread overview]
Message-ID: <marc-lartc-100742192804469@msgid-missing> (raw)
Hi Julian,
It looks like your patch is not compatible with FreeS/WAN's (1.92) patches.
Or at least in trying to compile a 2.2.20 kernel, it works fine with yours,
but then adding FreeS/WAN leads to errors. Word has it that FreeS/WAN 1.92
normally works with 2.2.20, but haven't verified that by experiment. Guess
it makes sense that you'd both be getting into some of the same sections of
kernel code.
I'm not saying this is something you should fix - I'm not all that impressed
with FreeS/WAN as an implementation (actually the commercial IPSec
implementations I've tested are also pretty flakey - hope that protocol
grows up some day). Just wanted to note to folks that there seems to be an
incompatibility here. In the long run, encrypted communications and good
redundant routing are both vital services.
Whit
@transpect.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-12-03 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 23:24 Whit Blauvelt [this message]
2001-12-03 23:34 ` [LARTC] more than 1 Line - but not with FreeS/WAN Julian Anastasov
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=marc-lartc-100742192804469@msgid-missing \
--to=whit@transpect.com \
--cc=lartc@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