netdev - Re: multicast with multiple devices

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.1.10.0806052024240.29055@fbirervta.pbzchgretzou.qr>
Date:	Thu, 5 Jun 2008 20:25:38 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	David Stevens <dlstevens@...ibm.com>
cc:	netdev@...r.kernel.org
Subject: Re: multicast with multiple devices


On Thursday 2008-06-05 19:25, David Stevens wrote:
>netdev-owner@...r.kernel.org wrote on 06/05/2008 02:54:54 AM:
>
>> But what if you do not have an application to begin with?
>> Does not the kernel do autonomic forwarding of multicast
>> like it does for unicast?
>
>        I'm not sure I understand your question, but if I
>do, then "no." The kernel uses multicasting itself on
>particular interfaces (e.g., with IPv6 neighbor discovery).
>Multicast packets are not forwarded unless the system
>is configured as a multicast router. Being a unicast
>router does not cause forwarding of multicast packets,
>and multicast routers maintain a completely separate
>routing table from the unicast routing table. Multicast
>routers and unicast routers need not be the same set
>of machines.
>        Really, multicast routing has nothing to do with
>unicast routing, and relying on the unicast routing
>table for multicast interface selection is usually
>just a source of application failures.

All I wanted to know is whether, and if s how, kernel-only
multicasting can be done, without the help of a userspace program
with perhaps the exception of setting up mc routes with iproute2.
Like..
  ip mr add 224/4 dev eth0
  ip mr add 224/4 dev eth1
and perhaps sysctl -w net.xyz.mc_forward=1, and the packets
should be routed --- ideally.
--
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