From: Andreas Hofmeister <andi@collax.com>
To: netdev@vger.kernel.org
Subject: Subnet router anycast for FE80/10 ?
Date: Mon, 31 Oct 2011 21:22:41 +0100 [thread overview]
Message-ID: <4EAF0391.80907@collax.com> (raw)
Hi,
I noticed that once forwarding has been enabled on an interface, there
is a "subnet router anycast address" for the link-local address prefix
FE80/10.
This address seems not to be explicitly mentioned in any RFC, but RFC
4291 says "All routers are required to support the Subnet-Router anycast
addresses for the subnets to which they have interfaces."
In the sense that a Linux router actually has an address FE80/10 on each
ipv6 enabled interface, it seems to be correct to also have FE80:: as an
anycast address on all interfaces which have ipv6 and forwarding enabled.
But then, FE80/10 is not actually supposed to be routed at all and so a
router cannot not really be a router for that particular subnet ?
Or is "FE80::" just supposed to be the anycast equivalent for the "all
routers" multicast address ff02::2 ?
Maybe someone on this list could enlighten me.
Ciao
Andi
next reply other threads:[~2011-10-31 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 20:22 Andreas Hofmeister [this message]
2011-11-02 15:38 ` Subnet router anycast for FE80/10 ? David Lamparter
2011-11-02 17:52 ` David Stevens
2011-11-02 21:53 ` David Lamparter
2011-11-02 23:27 ` David Stevens
2011-11-02 17:33 ` David Stevens
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=4EAF0391.80907@collax.com \
--to=andi@collax.com \
--cc=netdev@vger.kernel.org \
/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).