Netdev List
 help / color / mirror / Atom feed
From: Peter Bieringer <pb@bieringer.de>
To: netdev@oss.sgi.com
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: IPv4 tunneled over IPv6-IPsec?
Date: Sun, 27 Mar 2005 14:47:38 +0200	[thread overview]
Message-ID: <13B368C239630E8F2BA18AF3@[192.168.17.4]> (raw)
In-Reply-To: <E1DFUeO-0001IS-00@gondolin.me.apana.org.au>

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.


BTW: the reason why I'm looking for such support is the need to connect 
some "legacy" IPv4 islands over IPv6.

Regards,
	Peter
-- 
Dr. Peter Bieringer                     http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D               mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member  http://www.deepspace6.net/

  reply	other threads:[~2005-03-27 12:47 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 [this message]
2005-03-28 20:06     ` Michael H. Warfield

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='13B368C239630E8F2BA18AF3@[192.168.17.4]' \
    --to=pb@bieringer.de \
    --cc=herbert@gondor.apana.org.au \
    --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