Re: [Live-devel] Multicast Interface

> Haha! There are issues with gmail now? Not “now”. The stigma against unprofessional email addresses has existed for years (since people started using “@aol.com ” addresses). It’s clearly explained in the FAQ (that everyone is asked to read before posting to the mailing list

Re: [Live-devel] Multicast Interface

On Wed, Oct 29, 2014 at 2:02 PM, Ross Finlayson wrote: > Thanks for the reply. I know how routing works ;) > > > Well, your use of a “@gmail.com” email address announces to the world > that you don’t know much of anything (and it’s why your email to the list > is moderated). Just saying :-) > >

Re: [Live-devel] Multicast Interface

> Thanks for the reply. I know how routing works ;) Well, your use of a “@gmail.com ” email address announces to the world that you don’t know much of anything (and it’s why your email to the list is moderated). Just saying :-) > I have one single interface in AP mode and t

Re: [Live-devel] Multicast Interface

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 ma

Re: [Live-devel] Multicast Interface

> 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., h

[Live-devel] Multicast Interface

Hey all, 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 via `struct ip_mreqn`. It's fairly simple to do this when you know the interface name and interface IP ahead of time. See `man 7 ip` . I

Re: [Live-devel] Multicast Interface Addr

Some people definitely needed the current code for unicast streaming (to/from a specific IP address); that's why the code is there. If I were to make your suggested change, I'm sure I'd get complaints from other people. However, I think the following change will satisfy everyone. In "Groupso

Re: [Live-devel] Multicast Interface Addr

In any case, the current code ("bind()"ing to "ReceivingInterfaceAddr") is necessary for unicast streams to work properly (if "ReceivingInterfaceAddr" was set to something other than INADDR_ANY). Re: So when you make this change, you are not able to receive unicast data? My Fedora Core 5 syste

Re: [Live-devel] Multicast Interface Addr

Re: But my change does not disable the ability to change the interface from the default. The address parameter on the "bind" call specifies what destination addresses the socket will accept in the arriving packets. If you use INADDR_ANY, you can accept data which specifies any address as the

Re: [Live-devel] Multicast Interface Addr

We *do* allow "ReceivingInterfaceAddr" to be something besides INADDR_ANY. That's the whole point of the existing code. Re: But my change does not disable the ability to change the interface from the default. The address parameter on the "bind" call specifies what destination addresses the s

Re: [Live-devel] Multicast Interface Addr

Why would you not allow ReceivingInterfaceAddr to be something besides INADDR_ANY? We *do* allow "ReceivingInterfaceAddr" to be something besides INADDR_ANY. That's the whole point of the existing code. -- Ross Finlayson Live Networks, Inc. http://www.live555.com/

Re: [Live-devel] Multicast Interface Addr

Sorry, but I can't make this change. The existing code is the whole reason why we allow "ReceivingInterfaceAddr" to be something other than INADDR_ANY. Re: Do you have a different suggestion of what to try? Why would you not allow ReceivingInterfaceAddr to be something besides INADDR_ANY? I

Re: [Live-devel] Multicast Interface Addr (solution)

Sorry, but I can't make this change. The existing code is the whole reason why we allow "ReceivingInterfaceAddr" to be something other than INADDR_ANY. -- Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list live-dev

Re: [Live-devel] Multicast Interface Addr (solution)

Forgive my extra post, but maybe it would be easier to understand if you change the line to this: MAKE_SOCKADDR_IN(name, INADDR_ANY, port.num()); Xochitl___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/

Re: [Live-devel] Multicast Interface Addr (solution)

Thanks for your response, but I don't think this fixes the problem. Why bother setting the Sending- and ReceivingInterfaceAddr at all if you are going to get the address using multicast loopback first? When I try this in my system with multicast enabled on eth1 and eth0, the multicast loopback

Re: [Live-devel] Multicast Interface Addr

Try to get your loopback address before setting your listening interfaces, this fixed my problem David, Thanks for your response, but I don't think this fixes the problem. Why bother setting the Sending- and ReceivingInterfaceAddr at all if you are going to get the address using multicast loo

Re: [Live-devel] Multicast Interface Addr

regards, David > - Original Message - > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: [Live-devel] Multicast Interface Addr > Date: Wed, 30 May 2007 11:12:59 -0500 > > > I have an issue where if I set the Sending- and ReceivingInterfaceAddr to

[Live-devel] Multicast Interface Addr

I have an issue where if I set the Sending- and ReceivingInterfaceAddr to eth1, I cannot receive multicast data. I set them as the first 2 lines of my main() function like this: SendingInterfaceAddr = our_inet_addr("10.145.223.24"); ReceivingInterfaceAddr = our_inet_addr("10.145.223.24"); I have