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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 30 Nov 2011 15:38:37 +0800
From:	Li Wei <lw@...fujitsu.com>
To:	netdev <netdev@...r.kernel.org>
Subject: Is there any necessary to add multicast route for a loopback device?

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? 

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html