Multicast: Difference between revisions

Multicast (view source)

Revision as of 00:01, 15 March 2017

342 bytes added , 15 March 2017

m

clean up, typos fixed: paramaters → parameters

Reedy

editor

698

edits

Revision as of 00:05, 14 July 2015 (view source) Michael (talk \| contribs) (multicast draft)		Revision as of 00:01, 15 March 2017 (view source) Reedy (talk \| contribs) m (clean up, typos fixed: paramaters → parameters) Newer edit →
(5 intermediate revisions by 2 users not shown)
= FTTC = == Example for Debian GNU/Linux == Have extracted some ~~paramaters~~parameters from pppd, this may not work correctly if there is more than one instance. eval `tdbdump /var/run/pppd2.tdb \| grep CALL_FILE \| cut -d'"' -f2` Add a route to the multicast group on the device upon which PPPoE runs, aimed at the openreach modem~~. Also found to work without legacy unicast IP by adding a route~~: echo ip route add 234.81.130.4 dev $DEVICE === 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 multicast even ifwhere clients don't send IGMP join and leave correctly, but this also means the stream has to be manually started and stopped. For testing, using smcroute we can reflect the multicast to other attached networks. SMCroute does not configure the interface without a legacy IP, so can copy WAN address: smcroute -l $DEVICE 234.81.130.4 see for forwarding statistics: now ffmpeg, vlc or other client can be ran elsewhere on the internal network, if their ethernet interfaces do not have legacy ip addresses and the client does not specify an interface, use the <var>ip route</var>▼ cat /proc/net/ip_mr_cache && ip mroute show ▲now ffmpeg, vlc or other client can be ran elsewhere on the internal network, if their ethernet interfaces do not have legacy ip addresses and the client does not specify an interface for IGMP, use ~~the~~ <~~var~~code>ip route add 234.81.130.4</~~var~~code> on these devices with a device aiming towards the PPPoE host system. == Example Notes == This had been tested on several linux bridges for [http://ebtables.netfilter.org/examples/basic.html#ex_nobridge ebtables purposes], each on 802.1q vlan tags, on a managed ethernet switch where the other untagged port for PPPoE is connected to the openreach modem. = Further Reading = * [http://ideas.aa.net.uk/?ia=7937 Votes on the idea] * [http://www.revk.uk/2012/11/multicast.html AAISP Director on Multicast] [[Category:3rd Party Routers]]