All of lore.kernel.org
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: mika.liljeberg@welho.com (Mika Liljeberg)
Cc: pekkas@netcore.fi, davem@redhat.com, jmorris@redhat.com,
	netdev@oss.sgi.com
Subject: Re: Fw: [PATCH] IPv6: Allow 6to4 routes with SIT
Date: Thu, 17 Jul 2003 03:58:15 +0400 (MSD)	[thread overview]
Message-ID: <200307162358.DAA12485@dub.inr.ac.ru> (raw)
In-Reply-To: <1058398742.5778.26.camel@hades> from "Mika Liljeberg" at Jul 17, 2003 02:39:02 AM

Hello!

> So what's the background for having the hack to specify a tunnel EP with
> a gateway route?

Technically, it allows to avoid creating hundreds of devices to maintain lots
of tunnels.

Actually, it exists due to historical reasons. ipip and ipip6
tunnels used the trick from the very beginning.

But f.e. ipgre device was new, so it uses more correct approach:
actual mapping cross address families can be made via neighbour tables.
But this requires to know an IPv6 address of the nexthop.
Clean, but inconvenient. :-)

Alexey

      reply	other threads:[~2003-07-16 23:58 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
2003-07-16 23:28         ` kuznet
2003-07-16 23:39           ` Mika Liljeberg
2003-07-16 23:58             ` kuznet [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=200307162358.DAA12485@dub.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=davem@redhat.com \
    --cc=jmorris@redhat.com \
    --cc=mika.liljeberg@welho.com \
    --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 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.