netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Wei <lw@cn.fujitsu.com>
To: netdev <netdev@vger.kernel.org>
Subject: Is there any necessary to add multicast route for a loopback device?
Date: Wed, 30 Nov 2011 15:38:37 +0800	[thread overview]
Message-ID: <4ED5DD7D.10908@cn.fujitsu.com> (raw)

Hi all,

I found that since Fedora 15, it use systemd as the 'init'. When systemd start 
it would config the ipv6 address(::1/128) for 'lo' and start it. While adding 
this address to 'lo', kernel will call addrconf_add_mroute() to set a multicast
route for 'lo' with rt->dst.error = -ENETUNREACH. After that, when I send multi-
cast message, the route subsystem return a route with .error set to NETUNREACH.

Is there any necessary to add multicast route for a loopback device? 

             reply	other threads:[~2011-11-30  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30  7:38 Li Wei [this message]
2011-12-01  2:30 ` Is there any necessary to add multicast route for a loopback device? Li Wei
2011-12-01  3:35   ` David Miller
2011-12-01  4:31     ` Li Wei
2011-12-01  4:36       ` Eric Dumazet
2011-12-01  6:01         ` Li Wei

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=4ED5DD7D.10908@cn.fujitsu.com \
    --to=lw@cn.fujitsu.com \
    --cc=netdev@vger.kernel.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).