From: Mitsuru Chinen <mitch@linux.vnet.ibm.com>
To: Toyo Abe <tabe@miraclelinux.com>
Cc: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [GIT PULL net-next-2.6] IPv6 Updates
Date: Wed, 2 Jul 2008 19:59:34 +0900 [thread overview]
Message-ID: <20080702195934.754349fb.mitch@linux.vnet.ibm.com> (raw)
In-Reply-To: <486B2208.2000104@miraclelinux.com>
Hi Abe-san,
On Wed, 02 Jul 2008 15:36:56 +0900
Toyo Abe <tabe@miraclelinux.com> wrote:
> Hi,
>
> I have a question regarding this one.
>
> > commit e6a359e650a738f4e2387ca5570c546e03b7e29d
> > Author: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> > Date: Sat Jun 28 14:18:38 2008 +0900
> >
> > ipv6 addrconf: add accept_dad sysctl to control DAD operation.
> >
> > - If 0, disable DAD.
> > - If 1, perform DAD (default).
> > - If >1, perform DAD and disable IPv6 operation if DAD for MAC-based
> > link-local address has been failed (RFC4862 5.4.5).
> >
>
> I don't see why you set 1 as a default, so far.
> Any concerns on setting >1 as a default?
You may want to read this discussion:
- Linux IPv6 DAD not full conform to RFC 4862 ?
http://www.spinics.net/lists/netdev/msg52027.html
The conclusion is:
http://www.spinics.net/lists/netdev/msg52095.html
Best Regards,
----
Mitsuru Chinen <mitch@linux.vnet.ibm.com>
> Regards,
> -toyo
>
> YOSHIFUJI Hideaki / 吉藤英明 wrote:
> > Hello.
> >
> > Please consider pulling following changes on top of commit
> > 28f49d8fec19833672a6a813bfde0068fee50bc9
> > Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/linville/wireless-next-2.6
> > available at
> > git://git.linux-ipv6.org/gitroot/yoshfuji/linux-2.6-next.git net-next-2.6-v6ready-20080702
> >
> > Regards,
> >
> > --yoshfuji
> >
> > HEADLINES
> > ---------
> >
> > ipv6: Do not assign non-valid address on interface.
> > ipv6: Do not forward packets with the unspecified source address.
> > ipv6: Assume the loopback address in link-local scope.
> > ipv6: Add disable_ipv6 sysctl to disable IPv6 operaion on specific interface.
> > ipv6 addrconf: add accept_dad sysctl to control DAD operation.
> > ipv6 route: Prefer outgoing interface with source address assigned.
> >
> > DIFFSTAT
> > --------
> >
> > Documentation/networking/ip-sysctl.txt | 11 +++++++
> > include/linux/ipv6.h | 4 ++
> > net/ipv6/addrconf.c | 53 ++++++++++++++++++++++++++++++++
> > net/ipv6/ip6_input.c | 3 +-
> > net/ipv6/ip6_output.c | 10 +++++-
> > net/ipv6/route.c | 32 +++++++++++++------
> > 6 files changed, 101 insertions(+), 12 deletions(-)
> >
> --
> 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-07-02 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 3:39 [GIT PULL net-next-2.6] IPv6 Updates YOSHIFUJI Hideaki / 吉藤英明
2008-07-02 6:36 ` Toyo Abe
2008-07-02 10:59 ` Mitsuru Chinen [this message]
2008-07-02 16:46 ` Toyo Abe
2008-07-02 7:16 ` Naohiro Ooiwa
2008-07-02 9:46 ` YOSHIFUJI Hideaki / 吉藤英明
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=20080702195934.754349fb.mitch@linux.vnet.ibm.com \
--to=mitch@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tabe@miraclelinux.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 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).