From: "Michael H. Warfield" <mhw@wittsend.com>
To: Peter Bieringer <pb@bieringer.de>
Cc: mhw@wittsend.com, netdev@oss.sgi.com,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: IPv4 tunneled over IPv6-IPsec?
Date: Mon, 28 Mar 2005 15:06:31 -0500 [thread overview]
Message-ID: <1112040391.17216.44.camel@localhost.localdomain> (raw)
In-Reply-To: <13B368C239630E8F2BA18AF3@[192.168.17.4]>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
Hey Peter!
On Sun, 2005-03-27 at 14:47 +0200, Peter Bieringer wrote:
> Hi Herbert,
> thank you for quick reply.
> --On Sonntag, 27. März 2005 20:05 +1000 Herbert Xu
> <herbert@gondor.apana.org.au> wrote:
> > Peter Bieringer <pb@bieringer.de> wrote:
> >>
> >> I retry to play tunneling IPv4 over IPv6-IPsec. Afair it is still not
> >> working (support is missing in 2.6.x kernel), but for startup, I have
> >> already a patch for ipsec.conf parsing (pluto already has an option to
> >> do this):
> >
> > The native IPsec stack doesn't support IPv4 over IPv6 or IPv6 over
> > IPv4 SAs. It won't be able to do so unless major surgery is done
> > to the IPsec and IP stack.
> Hmm, looks like more a long term issue :-(
> So another question: what is the status of tunneling IPv4 over IPv6 without
> IPsec e.g. using GRE or special native tunneling? Similar issue? I digged a
> little bit around in GRE code and found some IPv6 references but no hints
> whether it can be used for that also.
You might want to check out the DSTM package here:
<http://www.ipv6.rennes.enst-bretagne.fr/dstm/>
That includes a tsp server as well as a 4over6 driver. Jim Bound is
the author/editor of record for the IETF draft on DSTM.
<http://www.ietf.org/internet-drafts/draft-bound-dstm-exp-02.txt>
I've had it spun up on some Linux systems in the past for testing
purposes. Unfortunately, it does not seem to be updated to build under
the 2.6 kernels. :-(
> BTW: the reason why I'm looking for such support is the need to connect
> some "legacy" IPv4 islands over IPv6.
> Regards,
> Peter
Mike
--
Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
prev parent reply other threads:[~2005-03-28 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 20:22 IPv4 tunneled over IPv6-IPsec? Peter Bieringer
2005-03-27 10:05 ` [Openswan dev] " Herbert Xu
2005-03-27 12:47 ` Peter Bieringer
2005-03-28 20:06 ` Michael H. Warfield [this message]
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=1112040391.17216.44.camel@localhost.localdomain \
--to=mhw@wittsend.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
--cc=pb@bieringer.de \
/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