From: kuznet@ms2.inr.ac.ru
To: mika.liljeberg@welho.com (Mika Liljeberg)
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: Thu, 17 Jul 2003 13:06:37 +0400 (MSD) [thread overview]
Message-ID: <200307170906.NAA13688@dub.inr.ac.ru> (raw)
In-Reply-To: <1058431132.5781.32.camel@hades> from "Mika Liljeberg" at Jul 17, 2003 11:38:53 AM
Hello!
> I'm not sure you can just remove these. It seems possible (?) to have
> the anycast address configured on one of the interfaces as a unicast at
> the same time. I.e., one of the anycast members could own the address.
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. But even that check is not necessary:
non-superuser may listen only for reserved unicasts, which are
excluded from allowed local addresses by policy. Kernel does not need even
to worry about this.
Actually, the test in ndisc.c was bogus by another reason:
inet_addr_type() checks only for reserved anycasts and non-reserved unicasts,
which would conflict with local addresses, were not detected in any case.
Alexey
next prev parent reply other threads:[~2003-07-17 9:06 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 ` kuznet [this message]
2003-07-17 9:32 ` Anycast usage, final diagnosis? (was: IPv6: Fix broken anycast Mika Liljeberg
[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=200307170906.NAA13688@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 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).