-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multicast #33
Comments
Yes, this sounds like a good idea. There are two aspects concerning the samplicator's functionality:
Sending seems more important for the goals you have in mind, but eventually receiving should also be supported, both for symmetry and for the practical purpose of being able to set up distribution trees using multiple samplicator processes, as people are doing now with unicast. I'm not sure the sending case even needs any code changes. Have you tried asking the samplicator to send to a multicast address? Spoofing the source address will often not work when redistributing packets to a multicast address, because multicast forwarding usually applies an RPF check. That should perhaps be mentioned in the documentation. |
It works. I can hear a sound stream via multicast, but many packets are lost. Unicast works much better than multicast, but I can't send to more than 3 destinations. It doesn't work: |
Can you tell me more about your situation? In particular, what kind of network do you have been the samplicator and the receivers? |
I have a 2.4GHz wireless network. The router (it is the samplicator) is an APU board http://www.pcengines.ch/apu.htm with 4GB RAM with and Debian system. The receivers are Android/iOS mobiles and Linux based laptops. |
Hi,-
in a large environment with multiple destinations, it would make sense simplicator to put the flow on multicast streams. i would reduce the processing power and bandwidth.
Any thoughts ?
thanks,
idsteiner
The text was updated successfully, but these errors were encountered: