<html><head></head><body>With NAT, also with carrier grade NAT becoming more poplular with ISP's yet to move to IPv6, if you have a very popular stream you could end up kicking valid listners behind the same IP.<br><br><br><div class="gmail_quote">On 23 December 2019 2:18:35 AM NZDT, Damian <db76@riseup.net> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hello fellow mailing list readers,<br><br>My question relates to multiple / duplicate connections to the ice cast server from the same IP address.<br><br>I am well aware that this is an issue that lies with the music player (listener agent) used by the listener. When a listener connects to the stream, sometimes it appears as two connections to the stream from the same IP address. This may last only a few seconds, or sometimes the listener may remain connected with two instances of the IP address. <br><br>I’d like some advice on what is best practice in dealing with these duplicate connections. Many years ago, when I ran a shoutcast server, a developer wrote a script for me that would automatically kick one of the duplicate connections, so that only the first connection remained tuned in to the stream. <br><br>I was considering reusing this script with the ice cast server. Would anyone advise against this practice? If so, for what reasons and would you advise an alteravie?<br><br>Regards<br>Damian<hr>Icecast mailing list<br>Icecast@xiph.org<br><a href="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</a><br></pre></blockquote></div><br>-- <br>Sent from Open Mail on Android.</body></html>