Open Network Stream selecting network interface

[kjrobinson08]

I have my laptop's wired ethernet connected directly to a video server play out a UDP multi-cast of 224.1.1.1 on port 8000. when I use vlc to view the stream I get an "cannot pre fill buffer". Wireshark has no problems seeing the stream so my source is ok.

I believe VLC is looking for the multi-cast on my wireless, when I disable it the following commands occur:
Your input can't be opened:
VLC is unable to open the MRL 'udp://@224.1.1.1:8000'

So I do I tell VLC to look for the multi-cast on my wired connection? I have tried the following commands(w/ and w/o the quotes) everytime I get "cannot pre fill buffer":
vlc udp://224.1.1.1:8000 --miface="eth0"
vlc udp://224.1.1.1:8000 --miface="192.168.0.199"
vlc udp://@224.1.1.1:8000 --miface="eth0"

I have also tried the following commands(w/ and w/o the quotes) everytime I get "invalid multicast interface: 192.168.0.199" error:
vlc udp://@224.1.1.1:8000 --miface="192.168.0.199"

I have no luck with using the GUI.
VLC media player 2.0.1 Twoflower (revision 2.0.1-0-gf432547) on Ubuntu 12.04 LTS

What is the correct command?

I have no problems when I use Windows 7 and the VLC GUI to view the same multi-cast off of the same video server.

[Rémi Denis-Courmont]

--miface=eth0 is correct. But make sure the protocol and port numbers are correct.

If it still fails, then check your local firewall settings. Some distributions block all inbound traffic by default.

[benou]

Hi,

Did you solve your problem ? I'm facing the same error with same version of VLC (2.0.1). However if using 1.0.6 (Goldeneye) the udp stream can be read without any problem.

[drc]

Hi,

Same issue here

if I open the stream with TSreader and run "vlc udp://@239.24.8.11:1234 --miface=10.27.7.2" is working if i close TSreader the stream is gone.

[jdwiegman]

Anyone have any luck with this? Its happening on my system too (Ubuntu VMware). My Windows host can pull it fine, and I am getting the stream in Wireshark.

[grayfox]

Been struggling with this problem for quite some time now, but a trick I found on another thread solved my issue: Simply add a route within your system to force traffic to go out on the proper interface (eth0/192.168.1.1) in my case:
//windows
route add 239.0.0.0 mask 255.0.0.0 192.168.1.1
//linux?
route add -net 239.0.0.0/8 dev eth0

By using wirehshark with igmp filter it is easy to check on which interface the igmp join traffic request is going out. If you see the join going on the correct iface but if you still do not receive your stream, it means there is another issue...

[jdwiegman]

I have this working by adding the multicast route: route add -net 224.0.0.0/4 dev eth0 (or whatever interface you want multicast on)