All of lore.kernel.org
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: pekkas@netcore.fi (Pekka Savola)
Cc: davem@redhat.com, netdev@oss.sgi.com
Subject: Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked
Date: Tue, 15 Jul 2003 18:46:57 +0400 (MSD)	[thread overview]
Message-ID: <200307151446.SAA08540@dub.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0307150906340.7445-100000@netcore.fi> from "Pekka Savola" at éÀÌ 15, 2003 09:14:07

Hello!

> "resolve" next-hops.  I.e., the requirement that the users/protocols will
> give you non-final nexthop information which you have to "resolve" to get
> the final nexthop (e.g. a global address -> a link-local address 
> obtained using Neighbor Discovery).

No way to resolve exists, unless it already embedded to corresponding protocol.
F.e. global address and its link-local equivalent could be transferred
as attributes of BGP4+, global address is used to validate nexthop attribute
and as soon as it happens to be on-link, its link-local counterpart is used.

If you have a global address out of context and want to use it as nexthop,
you are in troubles. You have no way to get a unique router identifier,
it is just not defined. So, you have to use global one (and kernel has to allow
this), and surely will screw up the network, unless some policy constraints
make the configuration legal.

Well, actually, we inevitably arrive to conclusion that all the idea
about scoped addresses is just a garbage, which results in nothing
but inconveniences and innumerous inconsistencies. I remember some
people predicted that it will be dropped to start of real Ipv6 deployment.
Well, it is still not night.

Alexey

  reply	other threads:[~2003-07-15 14:46 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030710.214551.08349572.davem@redhat.com>
2003-07-14 23:49 ` 2.4.21+ - IPv6 over IPv4 tunneling b0rked kuznet
2003-07-15  6:14   ` Pekka Savola
2003-07-15 14:46     ` kuznet [this message]
2003-07-15 17:29       ` Pekka Savola
2003-07-15 23:19         ` kuznet
2003-07-16  6:03           ` Pekka Savola
2003-07-17  0:03             ` kuznet
2003-07-17  6:50               ` Pekka Savola
2003-07-10 15:43 CaT
2003-07-10 15:55 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-10 15:58   ` CaT
2003-07-10 16:08   ` Pekka Savola
2003-07-13 14:49     ` Anand Kumria
2003-07-13 16:23       ` Pekka Savola
2003-07-10 19:57   ` Mika Penttilä
2003-07-10 16:27 ` Mika Liljeberg
2003-07-10 23:39   ` CaT
2003-07-11  0:04     ` Mika Liljeberg
2003-07-11  1:49       ` Andre Tomt
2003-07-11  2:03         ` Mika Liljeberg
2003-07-11  4:51         ` Pekka Savola
2003-07-11  5:20           ` Mika Liljeberg
2003-07-11  5:22             ` Pekka Savola
2003-07-11  5:39               ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11  8:46                 ` Pekka Savola
2003-07-11  9:04                   ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11  9:39                     ` Mika Penttilä
2003-07-11  9:39                       ` Mika Penttilä
2003-07-11 10:03                     ` Pekka Savola
2003-07-11 10:47                       ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 10:47                         ` Pekka Savola
2003-07-11 10:59                           ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 10:59                             ` Pekka Savola
2003-07-11 11:03                               ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 11:04                                 ` Pekka Savola
2003-07-11 11:36               ` Mika Liljeberg
2003-07-11 11:48                 ` Pekka Savola
2003-07-11 12:09                   ` Mika Liljeberg
2003-07-11 12:48                     ` Mika Penttilä
2003-07-11 13:38                       ` Mika Liljeberg
2003-07-11 14:27                         ` Mika Penttilä
2003-07-11 14:32                           ` Mika Liljeberg
2003-07-11 15:16                             ` Mika Penttilä

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=200307151446.SAA08540@dub.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=davem@redhat.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.