From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: Brian Haley <brian.haley@hp.com>, Jay Vosburgh <fubar@us.ibm.com>,
David Stevens <dlstevens@us.ibm.com>,
Alex Sidorenko <alexandre.sidorenko@hp.com>,
David Miller <davem@davemloft.net>,
Simon Horman <horms@verge.net.au>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
netdev-owner@vger.kernel.org,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH v2] bonding: send IPv6 neighbor advertisement on failover
Date: Fri, 10 Oct 2008 13:15:08 -0400 [thread overview]
Message-ID: <48EF8D9C.2040605@hp.com> (raw)
In-Reply-To: <1223657772.10489.5.camel@w-sridhar2.beaverton.ibm.com>
Sridhar Samudrala wrote:
> On Fri, 2008-10-10 at 12:29 -0400, Vlad Yasevich wrote:
>> Brian Haley wrote:
>>> Jay Vosburgh wrote:
>>>> As a semi-related question, what does IPv6 do if it receives a
>>>> gratutitous NA, and finds a duplicate?
>
> I think Jay was asking about the case where the target address in the NA
> matches the address of the receiving interface. The RFCs don't describe
> how to handle such a case and leave it to the implementation. Linux logs
> a warning message and ignores such NA.
>
Yes, but in this case, you have duplicate addresses configured. This
can happen when subnets merge and isn't really related to bonding driver.
In such a case, if we do an NS, it will trigger an NA and we'll end up
logging such a warning. If we do an NA, the other end, if it's linux, will
log this warning, or deal with it in its own manner.
So, it's really a draw.
-vlad
> Thanks
> Sridhar
>
>>> If a node has an IPv6 neighbor entry and receives an unsolicited NA it
>>> will change it's state to stale, forcing a re-lookup on the next
>>> transmit. An un-solicited NA will change the state to reachable.
>> ^^^^^^^^^^^^
>>
>> You probably meant to say "solicited". Unsolicited NAs can only change
>> the state to STALE.
>>
>> Also, the re-lookup will happen on a delay after the transmit.
>>
>> -vlad
>
>
next prev parent reply other threads:[~2008-10-10 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 0:52 [PATCH v2] bonding: send IPv6 neighbor advertisement on failover Brian Haley
2008-10-10 2:23 ` David Stevens
2008-10-10 14:34 ` Brian Haley
2008-10-10 15:03 ` David Stevens
2008-10-10 15:53 ` Jay Vosburgh
2008-10-10 16:04 ` Brian Haley
2008-10-10 16:29 ` Vlad Yasevich
2008-10-10 16:56 ` Sridhar Samudrala
2008-10-10 17:15 ` Vlad Yasevich [this message]
2008-10-10 15:27 ` Vlad Yasevich
2008-10-27 20:07 ` Brian Haley
2008-10-28 0:24 ` Jay Vosburgh
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=48EF8D9C.2040605@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=alexandre.sidorenko@hp.com \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=fubar@us.ibm.com \
--cc=horms@verge.net.au \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
--cc=yoshfuji@linux-ipv6.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 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.