From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Brian Haley <brian.haley@hp.com>
Cc: 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 12:29:06 -0400 [thread overview]
Message-ID: <48EF82D2.6030008@hp.com> (raw)
In-Reply-To: <48EF7CFF.4050405@hp.com>
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?
>
> 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
>
>> I agree that doing DAD would update the switches, peers, etc,
>> but, if I'm reading the IPv6 code correctly, the delay between probes is
>> one second (nd_tbl.retrans_time), and it looks like there's an initial
>> delay of up to 1 second as well (in addrconf_dad_kick, the
>> rtr_solicit_delay). For failover purposes, we want to issue the
>> gratuitous ARP or NA packets immediately with a minimal delay between
>> probes.
>
> Right, and since a bond failover event should be rare, I think sending
> the NA immediately is OK. All those random delays are meant to cover
> the case, for example, when a router sends an advertisement with a new
> prefix - you don't want everyone that receives it to do DAD immediately
> since it could overwhelm the network.
>
> -Brian
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-10-10 16:29 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 [this message]
2008-10-10 16:56 ` Sridhar Samudrala
2008-10-10 17:15 ` Vlad Yasevich
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=48EF82D2.6030008@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=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 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).