On Wed, Nov 19, 2014 at 12:52:10PM +0100, Michal Kubecek wrote:
>
> Handling Windows XP with IPv6 support will be more tricky. What might
> work would be to move the attempt to set IPV6_V6ONLY earlier, before
> getaddrinfo() is called, and also use AF_UNSPEC if setting IPV6_V6ONLY
> to 0 failed.
...which won't work as we can't try setsockopt() until we create the
socket and socket creation needs to wait for getaddrinfo() to tell us
what packet family to use. :-(
I guess there are three options:
1. Add the explanation and suggestion to use "RemoteBindAddress 0.0.0.0"
as workaround on pre-Vista Windows to Release Notes.
2. Let the server listen on 0.0.0.0 by default everywhere (so that admin
can change it where IPv6 is needed).
3. Add multiple sockets support, turn IPv6V6Only on by default and
interpret "" as "0.0.0.0;::" (if it is on).
Personally, I like option 1 most; the fact that systems needing the
workaround are either unsupported already (except for POS usage) or soon
to be might calm down our conscience.
Michal Kubecek
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
