[Live-devel] Multicast Interface

[Anthony Clark]

Ross,

Thanks for the reply. I know how routing works ;). Just to avoid the
back-and-forth. I have one single interface in AP mode and the kernel will
*never* choose it for mcast routing even though a route is present, mcast
is enabled, etc. I could use a tun/tap in theory, but I think that just
makes it more complicated. Being able to explicitly choose the mcast
interface avoids a lot of environment variation. If you think forcing an
interface is to be avoided, then I'll make the best and most practical
changes I can to live555/Groupsock and send in a patch just so you can see.
I appreciate the help, and live555 - it's great.



On Wed, Oct 29, 2014 at 1:26 AM, Ross Finlayson <finlayson at live555.com>
wrote:

> First off, I'm using the newest live555 and focusing only on linux. So,
> I'm interested in forcing Groupsock to send multicast from a specific
> interface
>
>
> The easiest (and most reliable) way to do this is to arrange for this
> interface to be the one that’s used for IP multicast routing - i.e., has a
> route for 224.0.0.0/4 .  You should be able to do this using the “route”
> command (type “man route”).
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20141029/35ef39c3/attachment.html>