From: Stuart Sheldon <stu@actusa.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: netdev@vger.kernel.org, Stuart Sheldon <stu@actusa.net>
Subject: Re: IPv6 Anycast?
Date: Thu, 22 Jul 2010 21:30:12 -0700 [thread overview]
Message-ID: <4C491AD4.9070103@actusa.net> (raw)
In-Reply-To: <alpine.DEB.1.10.1007230554240.9875@uplift.swm.pp.se>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Yea, I'm sure...
We use Linux for routers as well as servers and workstations. Since I
sent this I've discovered that by default, when a Linux system has IPv6
forwarding turned on, it adds the <network>::/64 anycast router
addresses on all the interfaces (as per rfc 2526).
What I'm actually looking to do is (change / add) other addresses the to
anycast6 list to work in an existing configuration that does not use the
rfc 2526 anycast router address.
Is there a command line method of setting up these anycast addresses?
Thanks,
Stu Sheldon
ACT USA
On 07/22/2010 08:57 PM, Mikael Abrahamsson wrote:
> On Thu, 22 Jul 2010, Stuart Sheldon wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Is IPv6 Anycast supported? And if so, how do I setup the Anycast
>> addresses?
>
> Are you sure that's what you're looking for?
>
> <http://en.wikipedia.org/wiki/Anycast>
>
> Because that's more a function of routing protocol/network, than
> anything really related to "netdev".
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJMSRrUAAoJEFKVLITDJSGSVnMP+wRF0jrC8RJn+C0EBlNl4uoW
qzEjGgrj7fqf9GOa5XWwVkoWHsZNyRZxJgNo73sS/s0PDwsFaZ11PWPqCSE1wafO
JkfKjhz3b7KOUjUNyYcvqzR45reRpoDUWVXpVYtqfzvCWvf6xdimatHFcKc3f14W
vX3rUG9BaWMuc74u/BZgKxpLXqTdXCwVIEXETSFGy63AdQSN9SIRlmgd6a60FGwJ
Cyr60Os8zAUDooQ++xwLB/ito6NdT7xAho2JRjejC0eblXYYT3bQU+kkS0qeHhYY
ucMuz18W6WswRM/wTnHzG7DvdRQNWMyvDvzR+qSQiAY6WMmwJ7qWfy1Ikj8l0QPe
5g0qI9Et/jOLzcwIrH2BAif8rBSpOHjqhXxhFNCtXyPsmIulZu4UzV1GbqV60Vp4
fixW4hgPDoqlwvfnojEZSVGxEy67GApokA7+TRY+sHQPvAhxA7b7WrT7liYgcW2B
4gTeaSbrvj6pw3ndYfrjOtbqlH29rU2RXi1MAhOq2fSrtIijMGZdKw6t5YbT5xik
qm3PRLYCzFocWP2sykjTds6VuHzhxm7+sqNe8p+0pyUoUYG9lNVyviMNHn0uz9L9
PDi8iIyDVHvEw6AHzmnmYc4RAz4Q/w/VxMY8jwjYurUnEyt9rtjMXsfv5rb2qkcB
cuyzbrEkx/49bRL+HZDx
=K4wA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-23 4:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 21:32 IPv6 Anycast? Stuart Sheldon
2010-07-23 3:57 ` Mikael Abrahamsson
2010-07-23 4:30 ` Stuart Sheldon [this message]
2010-07-23 5:51 ` Mikael Abrahamsson
2010-07-23 15:12 ` Stuart Sheldon
2010-07-23 16:29 ` Ulrich Weber
2010-07-23 16:54 ` Stuart Sheldon
2010-07-26 8:44 ` Simon Horman
2010-07-26 21:40 ` Stuart Sheldon
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=4C491AD4.9070103@actusa.net \
--to=stu@actusa.net \
--cc=netdev@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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.