Revision as of 23:29, 29 August 2022 (view source) Michael (talk \| contribs) (234.81.130.4 superseded with 234.81.131.194 and others) ← Older edit		Revision as of 23:41, 29 August 2022 (view source) Michael (talk \| contribs) m (→‎Relaying the stream) Newer edit →
=== 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. ~~For real use an IGMP proxy would be used but for first testing~~ [http://troglobit.github.io/smcroute smcroute] lets one ~~try~~forward multicast ~~even~~statically ~~where~~at ~~clients~~first ~~don't~~and ~~send~~can ~~IGMP~~even ~~join~~work ~~and~~where ~~leave~~programs ~~correctly,~~do ~~but~~not ~~this~~understand ~~also~~IGMP ~~means~~or ~~the~~even ~~stream~~multicast, ~~has~~which tocan be ~~manually~~aided ~~started~~with DNAT rules and ~~stopped.~~-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.

Multicast (view source)

Revision as of 23:41, 29 August 2022