From: "H. Peter Anvin" <hpa@zytor.com>
To: "Stephen J. Bevan" <stephen@dino.dnsalias.com>
Cc: netdev@vger.kernel.org
Subject: Re: ProxyARP and IPSec
Date: Mon, 04 Sep 2006 22:17:38 -0700 [thread overview]
Message-ID: <44FD0872.80104@zytor.com> (raw)
In-Reply-To: <17657.61339.125326.706889@localhost.localdomain>
Stephen J. Bevan wrote:
>
> > Really... if saying our configuration is so screwed up that we have to
> > run a different over-wire protocol isn't an admission of failure I don't
>
> If you use ipip the over-wire protocol is identical, see RFC 3884
> section 3.1 or you can test it right now using manual keying (remote
> side uses tunnel mode, your side uses transport + ipip). To use IKE
> pluto would need to be hacked a bit, though most of the changes could
> be handled via a updown script.
>
Interesting. It might be interesting to implement userspace (e.g.
OpenSwan) in such a way that all tunnel-mode IPsec is implemented this
way automatically, using an ipip interface in the kernel.
-hpa
next prev parent reply other threads:[~2006-09-05 5:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 0:31 ProxyARP and IPSec H. Peter Anvin
2006-08-23 19:14 ` Thomas Graf
2006-08-23 22:14 ` David Miller
2006-08-23 23:18 ` Alexey Kuznetsov
2006-08-24 1:12 ` H. Peter Anvin
2006-08-24 1:14 ` H. Peter Anvin
2006-08-24 2:20 ` Andy Gay
2006-08-24 4:14 ` H. Peter Anvin
2006-08-24 12:50 ` Alexey Kuznetsov
2006-08-26 4:16 ` H. Peter Anvin
2006-09-02 15:36 ` Stephen J. Bevan
2006-09-02 17:30 ` H. Peter Anvin
2006-09-02 20:54 ` Stephen J. Bevan
2006-09-05 5:17 ` H. Peter Anvin [this message]
2006-09-04 22:27 ` Alexey Kuznetsov
2006-09-05 5:12 ` H. Peter Anvin
2006-09-05 9:05 ` Alexey Kuznetsov
2006-09-22 20:36 ` David Miller
2006-09-23 4:22 ` Stephen J. Bevan
2006-09-06 2:25 ` Stephen J. Bevan
2006-08-24 10:50 ` Thomas Graf
2006-09-07 22:28 ` H. Peter Anvin
2006-09-08 7:37 ` Thomas Graf
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=44FD0872.80104@zytor.com \
--to=hpa@zytor.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@dino.dnsalias.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 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.