<div dir="ltr">Hm, I attempted to file a ticket but was rejected:<br><br>Submission rejected as potential spam <ul><li>BotScout says this is spam (Y|MULTI|IP|0|MAIL|0|NAME|2)</li><li>StopForumSpam says this is spam (username [40])</li></ul><p>Maybe because I just registered?<br></p></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 17, 2014 at 12:59 PM, Ralph Giles <span dir="ltr"><<a href="mailto:giles@thaumas.net" target="_blank">giles@thaumas.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2014-11-17 7:55 AM, RJ Ryan wrote:<br>
<br>
> They are requesting that libshout "fall back" on the ipv4 resolution of<br>
> the hostname if the ipv6 version fails to connect.<br>
<br>
</span>Binding only ipv4 on an dual-stack server is a deployment bug, but<br>
libshout should fall back when running on a dual-stack client, as they<br>
say. Please do file a bug.<br>
<br>
I believe RFC 6555 describes the current best practice for this: clients<br>
should probe over both protocols when dns returns both ipv6 and ipv4<br>
addresses and use whichever to work around breakage like this (which can<br>
occur at intermediate routers as well as at servers).<br>
<br>
The http module in the opusfile library has an implementation of this if<br>
you want code to borrow.<br>
<br>
-r<br>
_______________________________________________<br>
Icecast-dev mailing list<br>
<a href="mailto:Icecast-dev@xiph.org">Icecast-dev@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/icecast-dev" target="_blank">http://lists.xiph.org/mailman/listinfo/icecast-dev</a><br>
</blockquote></div><br></div>