<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">(last reply got rejected, so trying again w/o trimming response)</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Haven’t tried this, so grain of salt.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The protected RTSPServer constructor has a parameter for the socket FD.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think you could first, subclass the RTSPServer class so you can pass in your own socket fd.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Using system calls w/ C++ or using .NET, initialize your own socket bound to the NIC you prefer (don’t forget to set it to listen and set the correct socket options, like non-blocking…follow GenericMediaServer::setUpOurSocket path for exacts).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Pass your initialized socket to a new instance of your RTSPServer subclass.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you are initializing your socket in C#, I believe you can get the socket FD from socket.Handle.ToInt32() property…and don’t let the handle be destroyed (eg, store reference to Socket object).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">HTH,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-Jer<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="border:none;padding:0in"><b>From: </b><a href="mailto:warren@etr-usa.com">live-devel</a><br>
<b>Sent: </b>Tuesday, December 6, 2016 12:40 PM<br>
<b>To: </b><a href="mailto:live-devel@ns.live555.com">LIVE555 Streaming Media - development & use</a><br>
<b>Subject: </b>Re: [Live-devel] live-devel Digest, Vol 157, Issue 2 - Multiple NICs</p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">On Dec 6, 2016, at 11:55 AM, Weber, Patrick <Patrick.Weber@iecinfrared.com> wrote:<br>
> <br>
> 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)<br>
<br>
Not according to this SO answer:<br>
<br>
<a href="https://stackoverflow.com/questions/7333764/">https://stackoverflow.com/questions/7333764/</a><br>
<br>
You may be confusing network stack routing with ASP.NET routes. Very much not the same thing.<br>
<br>
> it would be so much nicer to just tell Live555 which NIC to use - either by IP or MAC address<br>
<br>
You may be able to play some games with bind() calls way down in the inner socket handling layers of Live555, but I wouldn’t recommend it.<br>
<br>
You’re asking us to help you second-guess an incorrect network stack routing setup instead of configuring it correctly.<br>
<br>
> instead of allowing Live555 to infer the NIC based on routing settings.<br>
<br>
Live555 infers nothing. It gives the packets to the network stack, and the network stack sends them out the network interface it decides is most appropriate based on the routing configuration.<br>
<br>
Go read Stevens or Quinn.<br>
_______________________________________________<br>
live-devel mailing list<br>
live-devel@lists.live555.com<br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>