From: kuznet@ms2.inr.ac.ru
To: pekkas@netcore.fi (Pekka Savola)
Cc: 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 04:20:46 +0400 (MSD) [thread overview]
Message-ID: <200307170020.EAA12924@dub.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0307160905330.20100-100000@netcore.fi> from "Pekka Savola" at Jul 16, 2003 09:12:04 AM
Hello!
> Yes, I dare to say that they're a requirement.
Nope. IPv6 host routing is based on assumption of link-locality
of the next hop. Probably, you want to read some rfcs or to look into code.
> the user space tools' problem: i.e. make them resolve a globally addressed
> nexthop to a link-local nexthop.
Impossible, as I said.
[ NOTE, the subject changed back to correct one at this point. Seems,
one sentence, written by me has grown to some huge tumor eating
original one completely. :-) ]
> specifications use and the *users* want and need to use.
Sigh, there no specifications about tricks used by Linux routing tables,
*users* are unlikely to want to use this feature at all, as Mika noticed.
And when they want, they want to right:
ip route add 3ffe::.... via 193.233.7.65
rather than crap sort of
ip route add 3ffe::.... via 2002:<something in latin>
I do not understand, what the hell is going on with you.
I am already sorry that started this. :-)
Alexey
next prev parent reply other threads:[~2003-07-17 0:20 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 [this message]
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
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=200307170020.EAA12924@dub.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=davem@redhat.com \
--cc=jmorris@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.