Thanks Warren. Unfortunately my scope of control ends at my application boundary. This application is video distribution of live camera feeds (surveillance system) and frequently our clients do not want us mucking around with their system settings. Clearly I *could* do what has been suggested from within my application (the top layer is C#/.NET, so the System.Web assembly has everything needed), but it would be so much nicer to just tell Live555 which NIC to use - either by IP or MAC address - instead of allowing Live555 to infer the NIC based on routing settings. But if that is my only option, then that is what I must do...
-----Original Message----- From: live-devel [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, December 5, 2016 3:00 PM To: [email protected] Subject: live-devel Digest, Vol 157, Issue 2 Send live-devel mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.live555.com/mailman/listinfo/live-devel or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of live-devel digest..." Today's Topics: 1. Re: live-devel Digest, Vol 157, Issue 1 (Weber, Patrick) 2. Re: live-devel Digest, Vol 157, Issue 1 (Warren Young) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Dec 2016 14:27:19 +0000 From: "Weber, Patrick" <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [Live-devel] live-devel Digest, Vol 157, Issue 1 Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Thanks for the response. Is there a non-default way (via C++ API) to select the NIC/IP address? My application may use multicast for other purposes (Web service discovery, for example), and I need to have it active on each NIC. -----Original Message----- From: live-devel [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, December 2, 2016 3:00 PM To: [email protected] Subject: live-devel Digest, Vol 157, Issue 1 Send live-devel mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.live555.com/mailman/listinfo/live-devel or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of live-devel digest..." Today's Topics: 1. Multiple NIC - RTSP URL. (Weber, Patrick) 2. Re: Multiple NIC - RTSP URL. (Ross Finlayson) ---------------------------------------------------------------------- Message: 1 Date: Fri, 2 Dec 2016 15:43:24 +0000 From: "Weber, Patrick" <[email protected]> To: "[email protected]" <[email protected]> Subject: [Live-devel] Multiple NIC - RTSP URL. Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" My application can have multiple NICs - how do I tell RTSPServer which IP address to use? Patrick Weber Principal Consultant [IAC Logo][mesa_recognized_practitioner_logo - Small] Integrated Automation Consulting LLC 440-552-5937 www.IntAutomation.com<http://www.intautomation.com/> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.live555.com/pipermail/live-devel/attachments/20161202/e5ee03de/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 2449 bytes Desc: image001.jpg URL: <http://lists.live555.com/pipermail/live-devel/attachments/20161202/e5ee03de/attachment-0002.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6755 bytes Desc: image002.jpg URL: <http://lists.live555.com/pipermail/live-devel/attachments/20161202/e5ee03de/attachment-0003.jpg> ------------------------------ Message: 2 Date: Sat, 3 Dec 2016 05:25:13 +1300 From: Ross Finlayson <[email protected]> To: LIVE555 Streaming Media - development & use <[email protected]> Subject: Re: [Live-devel] Multiple NIC - RTSP URL. Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 > On Dec 3, 2016, at 4:43 AM, Weber, Patrick <[email protected]> > wrote: > > My application can have multiple NICs ? how do I tell RTSPServer which IP > address to use? By default, the server uses the network interface that?s used for IP multicast routing - i.e., the one that has a route for 224.0.0.0/4. (The reason for this is that it uses IP multicast to detect its own IP address.) So, the easiest way to choose a particular network interface is to reconfigure your host so that it uses that network interface for IP multicast routing. You should be able to do this by running (as root): route add 224.0.0.0/4 ip-address-for-that-nic Ross Finlayson Live Networks, Inc. http://www.live555.com/ ------------------------------ Subject: Digest Footer _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel ------------------------------ End of live-devel Digest, Vol 157, Issue 1 ****************************************** ------------------------------ Message: 2 Date: Mon, 5 Dec 2016 12:00:15 -0700 From: Warren Young <[email protected]> To: LIVE555 Streaming Media - development & use <[email protected]> Subject: Re: [Live-devel] live-devel Digest, Vol 157, Issue 1 Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 On Dec 5, 2016, at 7:27 AM, Weber, Patrick <[email protected]> wrote: > > Thanks for the response. Is there a non-default way (via C++ API) to select > the NIC/IP address? My application may use multicast for other purposes (Web > service discovery, for example), and I need to have it active on each NIC. These services must use different addresses, which gives you the opportunity to route them separately. I suggest that you use the default rule Ross recommended for the ?best? interface for multicast, then add additional routes with lower metrics (see the netstat/route(8) manual page) for the exceptions. For example, let?s say you have IPTV going out on 239.255.{0-3}.x and you wanted it to go out the 1.2.3.4 interface. Let?s further say you have the 224/4 route on the 2.3.4.5 interface with metric 10. You could then say: route add 239.255.0.0/22 1.2.3.4 metric 9 That causes the network stack?s routing layer to prefer sending IPTV multicast packets out the 1.2.3.4 NIC while everything else goes out 2.3.4.5. ------------------------------ Subject: Digest Footer _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel ------------------------------ End of live-devel Digest, Vol 157, Issue 2 ****************************************** _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
