From: David Miller <davem@davemloft.net>
To: nhorman@tuxdriver.com
Cc: netdev@vger.kernel.org
Subject: Re: The mystery of optimistic ipv6 DAD handling
Date: Wed, 28 Dec 2011 14:38:12 -0500 (EST) [thread overview]
Message-ID: <20111228.143812.206477268839022030.davem@davemloft.net> (raw)
In-Reply-To: <20111228192150.GA16499@neilslaptop.think-freely.org>
From: Neil Horman <nhorman@tuxdriver.com>
Date: Wed, 28 Dec 2011 14:21:50 -0500
> Clearly I misread the RFC the first time through and the test as it existed is
> incorrect. I'm wondering though if what we need is a way to lookup if we've
> received a RA on the interface, and check to see if it has a source link layer
> option attached to it.
Yes, we could implement this with a new neigh lookup routine, that allows
keying on device pointer and flags.
So in this case we'd pass the device and NTF_ROUTER. If the lookup returns
non-NULL then we've seen an RA with SLLAO specified.
next prev parent reply other threads:[~2011-12-28 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 19:06 The mystery of optimistic ipv6 DAD handling David Miller
2011-12-27 19:53 ` David Miller
2011-12-28 15:19 ` Neil Horman
2011-12-28 18:39 ` David Miller
2011-12-28 19:21 ` Neil Horman
2011-12-28 19:38 ` David Miller [this message]
2011-12-29 0:00 ` Neil Horman
2012-01-03 19:45 ` Neil Horman
2012-01-03 19:48 ` David Miller
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=20111228.143812.206477268839022030.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/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).