Multicast: Difference between revisions
Appearance
Content deleted Content added
234.81.130.4 superseded with 234.81.131.194 and others |
|||
| Line 22: | Line 22: | ||
=== Relaying the stream === |
=== Relaying the stream === |
||
It may happen that the computer hosting PPPoE is in an inconvenient location for watching and that other networked devices should receive copies of the stream. |
It may happen that the computer hosting PPPoE is in an inconvenient location for watching and that other networked devices should receive copies of the stream. [http://troglobit.github.io/smcroute smcroute] lets one forward multicast statically at first and can even work where programs do not understand IGMP or even multicast, which can be aided with DNAT rules and -j REDIRECT |
||
Further work is to listen for for IGMP internally and "manage" smcroute, due to a possible linux limitation of only allowing one userspace program manage kernel mrouting at a time, to have maximum flexibility in upstreams and downstreams including internal sources. |
|||
Other software that may be useful is [https://manpages.debian.org/stable/igmpproxy igmpproxy] and [https://unfix.org/projects/ecmh/ ecmh] |
|||
For testing and usage, smcroute can reflect the multicast to other attached networks. The old SMCroute, would not configure the interface without an IP address on it, however the very latest smcroute allows 0.0.0.0 to be used to originate the IGMP3 joins, this needed the upgrade from ip_mreq to ip_mreqn in the smcroute code. |
For testing and usage, smcroute can reflect the multicast to other attached networks. The old SMCroute, would not configure the interface without an IP address on it, however the very latest smcroute allows 0.0.0.0 to be used to originate the IGMP3 joins, this needed the upgrade from ip_mreq to ip_mreqn in the smcroute code. |
||