From: Mika Liljeberg <mika.liljeberg@welho.com>
To: kuznet@ms2.inr.ac.ru
Cc: davem@redhat.com, jmorris@redhat.com, pekkas@netcore.fi,
netdev@oss.sgi.com
Subject: Re: Anycast usage, final diagnosis? (was: IPv6: Fix broken anycast
Date: 17 Jul 2003 12:32:33 +0300 [thread overview]
Message-ID: <1058434352.5780.44.camel@hades> (raw)
In-Reply-To: <200307170906.NAA13688@dub.inr.ac.ru>
On Thu, 2003-07-17 at 12:06, kuznet@ms2.inr.ac.ru wrote:
> They cannot intersect, otherwise RTF_LOCAL thing will not work.
>
> I deliberately blocked attempt to add a local address as anycast
> in anycast.c, see another chunk.
Ok, I missed that one.
I guess it's safe to assume that the anycast and unicast spaces will not
intersect, even though the addresses are allocated from the same range.
I was wondering how to dynamically assign anycast addresses. In theory
one could abuse the unicast address assignment mechanisms (in the
absence of anything else users might be tempted to try this). But that's
a different issue.
MikaL
next prev parent reply other threads:[~2003-07-17 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <no.id>
2003-07-17 2:23 ` Anycast usage, final diagnosis? (was: IPv6: Fix broken anycast usage) kuznet
2003-07-17 2:23 ` David S. Miller
2003-07-17 8:38 ` Mika Liljeberg
2003-07-17 9:06 ` Anycast usage, final diagnosis? (was: IPv6: Fix broken anycast kuznet
2003-07-17 9:32 ` Mika Liljeberg [this message]
[not found] <200307171030.OAA13906@dub.inr.ac.ru>
2003-07-17 10:41 ` Pekka Savola
[not found] ` <200307172052.AAA15032@dub.inr.ac.ru>
2003-07-17 21:51 ` David S. Miller
2003-07-17 22:28 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-18 6:44 ` Pekka Savola
2003-07-19 6:41 ` David S. Miller
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=1058434352.5780.44.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).