From: Felix Fischer <fischer@ikr.uni-stuttgart.de>
To: netdev@oss.sgi.com
Subject: IPv6 Tunneling (reverse tunnel need)
Date: Fri, 20 May 2005 13:19:59 +0200 [thread overview]
Message-ID: <200505201319.59707.fischer@ikr.uni-stuttgart.de> (raw)
I'm currently working on a research project and ran into a
question regarding tunneling/decapsulation in IPv6.
<------> [ A ] ===== tunnel from A to B =====> [ B ] <------->
Packets tunneled from A to B are only decapsulated at node B if
B has setup a tunnel-device in direction from B to A (reverse tunnel).
Is the need for the tunnel-device on node B an implementation
issue to handle tunneling, or does it come from something
else (i.e. standard requirement) ?
Further, I am wondering why the possibility to use the ANY_ADDRESS
as tunnel-end-point isn't present in IPv6 ?
The IPv4 implementation allows the usage of "0.0.0.0" as remote_address for
tunnel-end-points.
Any help would be greatly appreciated.
Regards,
Felix Fischer
--
-------------------------------------------------------------------
Institute of Communication Networks and Computer Engineering (IKR)
University of Stuttgart, Germany
-------------------------------------------------------------------
reply other threads:[~2005-05-20 11:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200505201319.59707.fischer@ikr.uni-stuttgart.de \
--to=fischer@ikr.uni-stuttgart.de \
--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