From: Mika Liljeberg <mika.liljeberg@welho.com>
To: kuznet@ms2.inr.ac.ru
Cc: kuznet <kuznet@dub.inr.ac.ru>,
davem@redhat.com, jmorris@redhat.com, pekkas@netcore.fi,
netdev@oss.sgi.com
Subject: Re: Anycast usage, final diagnosis? (was: IPv6: Fix broken anycast usage)
Date: 17 Jul 2003 11:38:53 +0300 [thread overview]
Message-ID: <1058431132.5781.32.camel@hades> (raw)
In-Reply-To: <200307170223.GAA13064@dub.inr.ac.ru>
Alexey,
On Thu, 2003-07-17 at 05:23, kuznet@ms2.inr.ac.ru wrote:
> diff -Nru a/net/ipv6/ndisc.c b/net/ipv6/ndisc.c
> --- a/net/ipv6/ndisc.c Thu Jul 17 06:13:09 2003
> +++ b/net/ipv6/ndisc.c Thu Jul 17 06:13:09 2003
> @@ -785,8 +785,7 @@
> ipv6_addr_all_nodes(&maddr);
> ndisc_send_na(dev, NULL, &maddr, &ifp->addr,
> ifp->idev->cnf.forwarding, 0,
> - ipv6_addr_type(&ifp->addr)&IPV6_ADDR_ANYCAST ? 0 : 1,
> - 1);
> + 1, 1);
> in6_ifa_put(ifp);
> return;
> }
> @@ -809,8 +808,7 @@
> if (neigh || !dev->hard_header) {
> ndisc_send_na(dev, neigh, saddr, &ifp->addr,
> ifp->idev->cnf.forwarding, 1,
> - ipv6_addr_type(&ifp->addr)&IPV6_ADDR_ANYCAST ? 0 : 1,
> - 1);
> + 1, 1);
> if (neigh)
> neigh_release(neigh);
> }
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.
For what it's worth, I think you have the right semantics.
MikaL
next prev parent reply other threads:[~2003-07-17 8:38 UTC|newest]
Thread overview: 5+ 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 [this message]
2003-07-17 9:06 ` Anycast usage, final diagnosis? (was: IPv6: Fix broken anycast kuznet
2003-07-17 9:32 ` Mika Liljeberg
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=1058431132.5781.32.camel@hades \
--to=mika.liljeberg@welho.com \
--cc=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=kuznet@dub.inr.ac.ru \
--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).