CERN Accelerating science

globus toolkit

Name of Supplier and/or Developer: 
"the Computation Institute", UChicago+ANL
Contact details for Supplier and/or Developer: 
http://www.globus.org, http://bugzilla.globus.org/
Version: 
5.2.5
Release date: 
Wednesday, October 30, 2013
Does developer claim IPv6 compliance?: 
Yes
Did you try running on dual stack system?: 
Yes
If so, did it break the application?: 
No
Does it bind to both stacks?: 
Yes
Is IPv6 preferred by default?: 
No
Can it be configured to prefer IPv6 or IPv4?: 
Yes
More information and/or link(s) to ticket(s): 
Up to Globus toolkit 5.2.3, the only way to have Globus IO and Globus FTP client library use/prefer IPv6 was via an API call (associated to the '-ipv6' option in globus-url-copy). 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. https://ggus.eu/ws/ticket_info.php?ticket=86101 http://jira.globus.org/browse/GT-32
Name of Tester: 
Francesco Prelz, francesco.prelz@mi.infn.it
Used by Experiment: 
ALICE
ATLAS
CMS
LHCb
How does it behave with a private IPv4 and a public IPv6?: 
Will prefer IPv6 as normally configured in /etc/gai.conf

Comments

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.,

GLOBUS_IO_IPV6=true
GLOBUS_FTP_CLIENT_IPV6=true

did not improve the behaviour.

Related tickets are