48
edits
Multicast: Difference between revisions
m
→Relaying the stream
(234.81.130.4 superseded with 234.81.131.194 and others) |
|||
| (5 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.
It may be possible later to have other programs listen for IGMP/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.
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.▼
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
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>
smcroutectl add $DEVICE 109.159.247.216 234.81.132.216 <var>int0 ext0</var>
To actually start, substituting for the other addresses beginning 234. above for the other channels.
smcroutectl join $DEVICE 234.81.131.194
| |||