From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: jbenc@redhat.com, netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH v2 net-next] ipv6: router reachability probing
Date: Wed, 11 Dec 2013 16:03:23 -0500 (EST) [thread overview]
Message-ID: <20131211.160323.283336557694027073.davem@davemloft.net> (raw)
In-Reply-To: <20131211191023.GA4675@order.stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Wed, 11 Dec 2013 20:10:23 +0100
> On Wed, Dec 11, 2013 at 01:48:20PM +0100, Jiri Benc wrote:
>> RFC 4191 states in 3.5:
>>
>> When a host avoids using any non-reachable router X and instead sends
>> a data packet to another router Y, and the host would have used
>> router X if router X were reachable, then the host SHOULD probe each
>> such router X's reachability by sending a single Neighbor
>> Solicitation to that router's address. A host MUST NOT probe a
>> router's reachability in the absence of useful traffic that the host
>> would have sent to the router if it were reachable. In any case,
>> these probes MUST be rate-limited to no more than one per minute per
>> router.
>>
>> Currently, when the neighbour corresponding to a router falls into
>> NUD_FAILED, it's never considered again. Introduce a new rt6_nud_state
>> value, RT6_NUD_FAIL_PROBE, which suggests the route should not be used but
>> should be probed with a single NS. The probe is ratelimited by the existing
>> code. To better distinguish meanings of the failure values, rename
>> RT6_NUD_FAIL_SOFT to RT6_NUD_FAIL_DO_RR.
>>
>> Signed-off-by: Jiri Benc <jbenc@redhat.com>
>
> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
>
> Looks good, thanks!
Applied, thanks guys.
next prev parent reply other threads:[~2013-12-11 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 12:48 [PATCH v2 net-next] ipv6: router reachability probing Jiri Benc
2013-12-11 19:10 ` Hannes Frederic Sowa
2013-12-11 21:03 ` David Miller [this message]
2013-12-11 23:12 ` Michal Kubecek
2013-12-12 0:56 ` David Miller
2013-12-12 1:26 ` Hannes Frederic Sowa
2013-12-12 1:21 ` Hannes Frederic Sowa
2013-12-12 9:10 ` Michal Kubecek
2013-12-12 19:08 ` Hannes Frederic Sowa
2013-12-13 12:51 ` Michal Kubecek
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=20131211.160323.283336557694027073.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jbenc@redhat.com \
--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).