From: Mika Liljeberg <mika.liljeberg@welho.com>
To: kuznet@ms2.inr.ac.ru
Cc: Pekka Savola <pekkas@netcore.fi>,
davem@redhat.com, jmorris@redhat.com, netdev@oss.sgi.com
Subject: Re: Fw: [PATCH] IPv6: Allow 6to4 routes with SIT
Date: 17 Jul 2003 01:28:58 +0300 [thread overview]
Message-ID: <1058394538.5778.17.camel@hades> (raw)
In-Reply-To: <200307151428.SAA08491@dub.inr.ac.ru>
Alexey,
> And this silly combination is still _better_ than 6to4 address, which
> contains redundant information, which can be mixed up with real _IPv6_
> 6to4 addresses and whihc contains IPv4 address in some place which
> used to be identification of a network prefix.
While I see where you're coming from, I don't really understand what the
fuss is all about.
IMHO, the real hack is being able to specify the tunnel endpoint using a
gateway route in the first place. Whether that gateway address is
IPv4-compatible or a 6to4 address is just a minor detail. I view my
patch as a simple convenience to the user, extending a hack that already
exists.
A more "correct" way would be to specify the gateway address in the
remote address field of the point-to-point SIT interface, and live with
the fact that you need a separate SIT interface for each 6to4 gateway
that you want to tunnel to. This already works, so the IPv4-compat route
hack is actually redundant. My understanding was that it is there simply
for convenience.
MikaL
next prev parent reply other threads:[~2003-07-16 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030713005345.1fea1092.davem@redhat.com>
2003-07-14 23:29 ` Fw: [PATCH] IPv6: Allow 6to4 routes with SIT kuznet
2003-07-15 6:28 ` Pekka Savola
2003-07-15 14:28 ` kuznet
2003-07-15 19:26 ` Pekka Savola
2003-07-15 23:32 ` kuznet
2003-07-16 6:12 ` Pekka Savola
2003-07-17 0:20 ` kuznet
2003-07-17 7:04 ` Pekka Savola
2003-07-17 11:16 ` Mika Liljeberg
2003-07-17 11:54 ` Mika Liljeberg
2003-07-17 13:55 ` Pekka Savola
2003-07-17 14:35 ` Mika Liljeberg
2003-07-16 22:28 ` Mika Liljeberg [this message]
2003-07-16 23:28 ` kuznet
2003-07-16 23:39 ` Mika Liljeberg
2003-07-16 23:58 ` kuznet
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=1058394538.5778.17.camel@hades \
--to=mika.liljeberg@welho.com \
--cc=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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;
as well as URLs for NNTP newsgroup(s).