Tiny Core Base > TCB Q&A Forum
Using a Tiny Core client as an IGMP host
RogerWilco:
I was wanting to test the IGMP/PIM features of vEOS, and I wasn't able to get both the Tinycore clients, and Debian Jessie server to use multicast to send a VLC stream via a multicast stream. Is there something specific I need to do to get the tinycore clients configured to accomodate IGMP, or is there a .tcz extension that would let me simulate this? I configured the vEOS switches correctly, but I never saw join/prune requests on the RP, nor would the client machines pull down the video I wanted to multicast.
Here's an example of the setup -> VLC-server
|
FHR
/ \
RP L3 Router
\ /
LHR
|
L2
TC-host 1 TC-host 2
I also tied directly connecting the hosts to LHR, but nada. Neither of the hosts could every see the video stream from the VLC server, and I never saw join, prune, registration, nor could the clients ping the multicast group address. I also tried IGMP host-proxy, but that was a no go.
curaga:
I can tell the kernel support is there, but otherwise I've never used multicast, sorry.
RogerWilco:
Darn! Thanks anyway curaga! :-\
Rich:
Hi RogerWilco
Have you looked at this:
http://peakdrive.com/?p=440
Some of the replies in the Comments section at the end may also be of use.
RogerWilco:
Hi Rich! I've been able to configure VLC to use rtp properly on my Debian Jessie server, but the Tiny Core clients never receive the stream, nor do I see any joins, registration, prunes on the Rendevous Point. It could easily be a configuration issue on my Tiny Core clients (or an issue with the vEOS switches). If I set all the switches to no use IGMP/PIM, and for direct routing, the Tiny Core clients can stream the VLC stream just fine (albeit slowly). The TC clients also cannot ping the multicast group address, which is why I'm wondering if it's just a misconfig in those.
Any idea what settings I need to add to ifconfig on the TC hosts to get them to reach the multicast group? I followed a generic linux example online about adding a multicast gw with "sudo route add", but I've no idea if I did it correct.
Navigation
[0] Message Index
[#] Next page
Go to full version