Updated to version 2.10 which is fully compliant.
If you have something like this in your PoolManager config:
psu create unit -net 0.0.0.0/0.0.0.0
psu addto ugroup world-net 0.0.0.0/0.0.0.0
You may need to add this:
psu create unit -net ::/0
psu addto ugroup world-net ::/0
after updating globus-ftp-client from v8.19 to v8.21 FTS3 transfers to IPv6-only site failed.
This was caused by the gridftp-transfers not being initiated in EPSV - which supports IPv6 - but falling back to passive mode PASV without IPv6 support. The behavior can be reproduced by up/downgrading the globus-ftp-client between v8.19 and v8.21.
Explicitly exporting globus parameters for enabling IPv6 in globus into the FTS environment, e.g.,
did not improve the behaviour.
Related tickets are
As of Globus 5.2.4, IPv6 can be enabled for Globus I/O by setting the GLOBUS_IO_IPV6 environment variable (to any value).
As of Globus 5.2.5, IPv6 can be enabled for Globus FTP as well by setting the GLOBUS_FTP_CLIENT_IPV6 environment variable (to any value).
More details in the following tickets.
- Microsoft Windows platforms are not supported.
- Mixed IPv4/IPv6 pools are not supported.
- Security policies cannot use IP addresses, only host names. If using NO_DNS=TRUE, the host names are reformatted IP addresses, and can be matched against those.
- NETWORK_INTERFACE must be set to a specific IPv6 address. It is not possible to use multiple IPv6 interfaces on a single computer.
- There must be valid IPv6 (AAAA) DNS and reverse DNS records for the computers. Setting the configuration NO_DNS=TRUE removes this limitation.
There is some UDP multicast data location stuff which is definitely not IPv6 compliant, but as far as I'm aware no one used that for production. The rest of the networking for GridSite is all done by Apache so I expect it will be ok.
Gridsite is used by the WMS and that works on dual-stack hosts.