From: David Miller <davem@davemloft.net>
To: wangxingtong@cn.fujitsu.com
Cc: gaofeng@cn.fujitsu.com, netdev@vger.kernel.org
Subject: Re: [PATCH V2] IPv6 : add multicast routing verify which net_device is lo
Date: Wed, 21 Dec 2011 14:11:38 -0500 (EST) [thread overview]
Message-ID: <20111221.141138.2054196549674078174.davem@davemloft.net> (raw)
In-Reply-To: <4EF1A061.5030005@cn.fujitsu.com>
From: Wang Xingtong <wangxingtong@cn.fujitsu.com>
Date: Wed, 21 Dec 2011 17:01:21 +0800
> OK, David, I reproduce this as following :
>
> 1) ip -6 route show | grep ff00
> unreachable ff00::/8 dev lo metric 1024 error -101
> ff00::/8 dev eth1 metric 1024
>
> 2) ip -6 route del ff00::/8 dev eth1
> ip -6 route del ff00::/8 dev lo
>
> 3) ip -6 route add ff00::/8 dev lo
> ip -6 route add ff00::/8 dev eth1
My answer is "Don't ever do that." The kernel sets up the
loopback device with all the necessary parameters you need
including the address, network prefix, and (once we revert
the recent bogus ipv6 autoconf patch) the multicast prefix.
There is no reason to ever explicit set the things that the
kernel takes care of for you.
That was exactly my point, the piece of userspace that has
started doing this needs to be fixed and we need to revert
Li Wei's recent patch.
prev parent reply other threads:[~2011-12-21 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 6:13 [PATCH] IPv6 : add multicast routing verify which net_device is lo Wang Xingtong
2011-12-20 9:47 ` Wang Xingtong
2011-12-20 11:10 ` [PATCH V2] " Gao feng
2011-12-21 6:15 ` David Miller
2011-12-21 9:01 ` Wang Xingtong
2011-12-21 19:11 ` David Miller [this message]
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=20111221.141138.2054196549674078174.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gaofeng@cn.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=wangxingtong@cn.fujitsu.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).