Multicast: Difference between revisions

← Older edit

Multicast (view source)

Revision as of 23:56, 29 August 2022

75 bytes added , 29 August 2022

m

→‎Relaying the stream

Michael

48

edits

Revision as of 23:51, 29 August 2022 (view source) Michael (talk \| contribs) mNo edit summary ← Older edit		Latest revision as of 23:56, 29 August 2022 (view source) Michael (talk \| contribs) m (→‎Relaying the stream)
(2 intermediate revisions by the same user not shown)
=== 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. [http://troglobit.github.io/smcroute smcroute] lets one forward multicast statically at first and can even work where programs do not understand IGMP or in some situations even multicast, which can be aided with DNAT rules and/or use of -j REDIRECT on targets ~~Further~~It ~~work~~may isbe possible later to have other programs listen ~~for~~ for IGMP ~~internally~~/MLD and then "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] Additionally the sysctl rp_filter is disabled on $DEVICE and "all" to allow the incoming multicast without a matching outgoing route, also desirable. iptables and/or nftables would still be used to filter. smcroute requires the source address, this was found with wireshark or tcpdump, and could be subject to change, <var>int0</var> and <var>ext0</var> are example devices to copy multicast packets to, these could be internal vlans on a home network: smcroutectl add $DEVICE 109.159.247.194 234.81.131.194 <var>int0 ext0</var>