Multicasting floods my network

[XstreamIP]

Hello:

Initial experiments with multicasting have flooded my network to the point where access to the Internet is "choked" off.

Is there a way to prevent this?

[Tikker]

unicast instead of multicast maybe

[Manaouf]

unicast instead of multicast maybe

For sure that multicast floods the network. Use unicast instead.[/b]

[shanson29]

I had a similar issue, multicasting a full mpeg2 stream from a haupauge PVR-250 over a 154MB ATM backbone. This would eventually cause the CPUs on the routers to peg at 100%.

Transcoding like this
--sout '#transcode{vcodec=mp4v,acodec=mp4a,ab=32,deinterlace,channels=2}:standard{access=udp{ttl=5}, mux=ts, dst=224.2.1.51}' -I http --daemon

reduced bandwidth to ~750kbps which we stream to 8 geographically diverse campuses.

I compiled VLC with plugins disabled as a ActiveX control for viewing in IE to avoid having to install the full client on 4000 workstations.

I love vlc (currently 0.8.6-svn)

[bXn]

I think it exists solutions using a kind of tunnel to reduce
bandwith consumption :

Code: Select all

|| || UDP/RTP multicast stream in a sub network A || || [tunnel front-end side A ] | | | RTP/ UDP or TDP unicast streams | | [tunnel front-end side B ] || || UDP/RTP multicast stream in a sub network B || ||

using this kind of architecture, you are doing
unicast between your remote "head-ends"
(with this kind of solution you can also bypass
some Firewalls restrictions between point A
and point B)