OK,<div>I dug a little and kind of found the answer why it works without a kernel patch</div><div><br></div><div>The apps that worked actually use bind() which is not the right way to do it, but it seems to work, both on linux and bsd.</div>
<div><br></div><div>Someone posted an example here for an older version of the lib as a workaround solution.</div><div><a href="http://www.mail-archive.com/live-devel@lists.live555.com/msg02194.html">http://www.mail-archive.com/live-devel@lists.live555.com/msg02194.html</a></div>
<div><br></div><div>What would the workaround be if I want to temporally patch the lib as it is today so it works ?<br>A see there is an IF for WIN, is there a way to make such a workaround for linux and what would the code be.</div>
<div>Sorry, I am a bit of C++ beginner when it comes to the library stuff.</div><div><br></div><div>Needles to say its hard to patch every kernel that comes with every distro packaged and gets updated every 2 weeks</div>
<div>Most people ise stock distro provided kernel, patching it is quite an effort. </div><div>Also why is this patch still not in the latest production kernels. I don't get it. Its a known issue, patches provided, why not in yet ?</div>
<div>While I do agree the OS is broken so is Windows, is there a way to test this and if the bug exists apply a workaround. </div><div>I am sure the biggest percentage of people use this lib under Linux.</div><div><br></div>
<div>Zed<br><div class="gmail_quote">On Sun, Sep 19, 2010 at 4:57 PM, Zdenek Bouresh <span dir="ltr"><<a href="mailto:zdenek@next-stream.com">zdenek@next-stream.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Thanks Ross, <div>I will try freeBSD and report back. </div><div><br></div><div>The part that I don't get is how do other apps don't get this problem on the same OS with the same input streams. </div><div><a href="http://239.255.1.1:22334" target="_blank">239.255.1.1:22334</a></div>
<div><a href="http://239.255.1.2:22334" target="_blank">239.255.1.2:22334</a></div><div><a href="http://239.255.1.3:22334" target="_blank">239.255.1.3:22334</a></div><div><br></div><div>All are recognized as different sources, since the combination of multicast IP and port is unique.</div>
<div>They all subscribe to all addresses, but when reading the requested socket, they read the one selected on the port, not the others. </div><div><br></div><div>From what I understand you're saying that when live555 is requested to read on port 22334 of some source, traffic there is coming from all sources and not just the requested. </div>
<div><br></div><div>Again, I dont get it, how do other apps work if this be the case.</div><div>Its this that leads me to believe that even if there is an OS problem, there is some way around it in code.</div><div><br></div>
<div>Thanks again, </div><div>Appreciate your time.</div><div>I will try freeBSD.</div><div><br></div><div>Zed.</div><div><br></div><div><div><div></div><div class="h5"><div class="gmail_quote">On Sun, Sep 19, 2010 at 3:12 PM, Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If your application is receiving - on a socket - traffic that was sent to a multicast address that that socket did not subscribe to, then that is definitely a problem with the operating system, not with your application, and not with our libraries.<br>
<br>
Because you say that you are unwilling to change your operating system[*], and because you say that you can't stop your incoming traffic (for different multicast addresses) from using distinct port numbers, then there's no help that I can give you. Sorry.<br>
<br>
[*] Note that FreeBSD - as far as I can tell - does not appear to have this problem. If I were you, I'd try using FreeBSD instead of Linux.<br>
-- <br><font color="#888888">
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" target="_blank">http://www.live555.com/</a><br>
_______________________________________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com" target="_blank">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
</font></blockquote></div><br><br clear="all"><br></div></div>-- <br>Zdenek Bouresh<br>NextStream LTD.<br><br>The information contained within this email transmission and any attachments is confidential and intended solely for the attention and use of the named individual addressee(s) or entity. It may not be legally revealed or be disclosed to any other person or third party without the express authority (prior written approval) of NextStream LTD and/or the original recipient, or the intended recipients, or both. If you are not the intended recipient, you must not disclose, copy, distribute, print, rely on or retain this message or any part of it. The information contained within is strictly prohibited. If you have received this email in error please notify the sender by reply, and delete this message from your email system(s). Any hard copies must also be destroyed.<br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Zdenek Bouresh<br>NextStream LTD.<br><br>The information contained within this email transmission and any attachments is confidential and intended solely for the attention and use of the named individual addressee(s) or entity. It may not be legally revealed or be disclosed to any other person or third party without the express authority (prior written approval) of NextStream LTD and/or the original recipient, or the intended recipients, or both. If you are not the intended recipient, you must not disclose, copy, distribute, print, rely on or retain this message or any part of it. The information contained within is strictly prohibited. If you have received this email in error please notify the sender by reply, and delete this message from your email system(s). Any hard copies must also be destroyed.<br>
</div>