[sclug] Playing with video (DVB-T)

Jason Rivers jason at jasonrivers.co.uk
Mon Jul 9 11:00:43 UTC 2012


 

On 09.07.2012 11:51, David Kerrawn wrote: 

>> -----Original
Message----- From: sclug-bounces at sclug.org.uk [1]
[mailto:sclug-bounces at sclug.org.uk [2]] On Behalf Of Jason Rivers Sent:
09 July 2012 10:34 To: sclug at sclug.org.uk [3] Subject: [sclug] Playing
with video (DVB-T) I've been playing with video streaming lately, so
that while my flatmate is watching some crap on TV I can still watch
something else... I have a system with 2 DVB-T tuners, I'll just start
with 1 card, tuned to 666000000 which allows me to get all the BBC
goodness and currently using DVBlast to get all the channels over the
network on Multicast (seperate Multicast IP for each channel). E.G.
rtp://239.255.1.1:5004 ##BBC1 rtp://239.255.1.2:5004 ##BBC2
rtp://239.255.1.3:5004 ##BBC3 rtp://239.255.1.4:5004 ##BBC4 etc.. The
problem with using Multicast is that it completely swamps my Wifi (to
the point that any wireless devices just disconnect and it's game over
for them). DVBlast only uses Multicast address's - This is just the way
it's designed to work. I'm wondering if anyone has any experience of
this, and if there's a better application to use so that I can host the
RTP streams from the machines IP (either single IP and multiple
ports/streams or multiple IP's are fine) and not using Multicast
(because of the Wifi). - I tried using cvlc - but I couldn't see a way
to have it use multiple channels (programs) successfully. Alternatively
I might just need to work out how to force the Multicast not to hit the
Wifi, I have a Billion 7800N currently, (it was one of the original test
routers from A&A that did IPv6). and can't see any option on the router
to block multicast over wifi (and I can't split the Wired/Wireless on
the firewal) I'm happy to change this to something like a Routerboard if
I need to, but I'd rather find a better way of doing it. Any tips on
different software to run the RTP stream without Multicast but with
multiple channels still would be great... Jason. P.S. dvblast also sends
out the channel guide over the RTP feed from the DVB-T feed, which is
very useful, but not critical...
> 
> You could do with something like
RFC4541: Considerations for Internet Group Management Protocol (IGMP)
and Multicast Listener Discovery (MLD) Snooping Switches
> 
> Where
Multicast doesn't hit a switch port unless a client has requested to
listen for it on that port.
> 
> http://tools.ietf.org/html/rfc4541
>
It's on MicroTik's Feature Requests page as Not Yet Implemented.
>
http://wiki.mikrotik.com/wiki/MikroTik_RouterOS/Feature_Requests
> 
>
Unfortunately I can't tell you where you can find it.
> Davek.

Would
that not still swamp the WiFi? - particularly if you called the RTP over
a WiFi device, that would then swamp the wireless AP... 

So far, the
only thing I can really think of doing is having a separate wireless AP
on a separate network with a route between that and the main network
(not bridged, as the Multicast would then go onto the WiFi there, too
IIRC). This isn't the best solution for "the home" especially one that
doesn't have NAT and would have to be really nice and ask for more
IP's.... :) 

Links:
------
[1] mailto:sclug-bounces at sclug.org.uk
[2]
mailto:sclug-bounces at sclug.org.uk
[3] mailto:sclug at sclug.org.uk



More information about the Sclug mailing list