Middleware

Enstore

Submitted by flopez on Tue, 05/05/2015 - 10:28
IPv6 Compliance
Name of Supplier and/or Developer
FNAL
Version
4.2.2
Release date
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?
Don't know/not tested
Can it be configured to prefer IPv6 or IPv4?
Don't know/not tested
Name of Tester
Fernando Lopez
Type
Middleware

dCache

Submitted by flopez on Thu, 05/08/2014 - 16:29
IPv6 Compliance
Are the logs IPv6 compliant?
Yes
Name of Supplier and/or Developer
dCache team
Contact details for Supplier and/or Developer
support@dcache.org
Version
2.10
Release date
Does developer claim IPv6 compliance?
Yes
From which version of the application does the developer claim IPv6 compliance?
2.2.0
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?
Yes
Can it be configured to prefer IPv6 or IPv4?
Yes
Name of Tester
Fernando Lopez (flopez@pic.es) Ulf Tigerstedt (ulf.tigerstedt@csc.fi)
Type
Middleware
Used by Experiment
ALICE
ATLAS
CMS
LHCb
How does it behave with a private IPv4 and a public IPv6?
It keeps to the protocol initially connected with.

VOMS-Admin

Submitted by Anonymous (not verified) on Fri, 01/24/2014 - 10:19
IPv6 Compliance
Version
3.3.1
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?
Don't know/not tested
Can it be configured to prefer IPv6 or IPv4?
Don't know/not tested
Type
Middleware
Used by Experiment
ALICE
ATLAS
CMS
LHCb

globus toolkit

Submitted by fprelz on Thu, 01/23/2014 - 14:04
IPv6 Compliance

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

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
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
Type
Middleware
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

xrootd

Submitted by sciaba on Mon, 11/25/2013 - 11:24
IPv6 Compliance
Contact details for Supplier and/or Developer
Andy Hanushevsky
Version
4.0.0
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?
Yes
Can it be configured to prefer IPv6 or IPv4?
Don't know/not tested
Type
Middleware
Used by Experiment
ALICE
ATLAS
CMS
LHCb
How does it behave with a private IPv4 and a public IPv6?
It will always advertise any IPv4 in preference of any IPv6 address, even when initially connected to with IPv6.

GUMS

Submitted by sciaba on Thu, 10/24/2013 - 14:36
IPv6 Compliance
Name of Supplier and/or Developer
OSG
Does developer claim IPv6 compliance?
Don't know
Type
Middleware
Used by Experiment
ATLAS
CMS

Hadoop

Submitted by sciaba on Thu, 10/24/2013 - 14:31
IPv6 Compliance
Name of Supplier and/or Developer
Apache
Contact details for Supplier and/or Developer
Brian Bockelman
Does developer claim IPv6 compliance?
No
Type
Middleware
Used by Experiment
ATLAS
CMS

HTCondor

Submitted by sciaba on Fri, 09/13/2013 - 10:37
IPv6 Compliance
Name of Supplier and/or Developer
University of Wisconsin–Madison
Does developer claim IPv6 compliance?
Don't know
From which version of the application does the developer claim IPv6 compliance?
7.7.5
Does it bind to both stacks?
Don't know/not tested
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)
IPv6 is supported with limitations (as of version 8.1):
- 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.
Type
Middleware
Used by Experiment
ATLAS
CMS

BestMAN

Submitted by scampana on Wed, 09/04/2013 - 15:34
IPv6 Compliance
Does developer claim IPv6 compliance?
Don't know
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?
Don't know/not tested
Can it be configured to prefer IPv6 or IPv4?
Don't know/not tested
Type
Middleware
Used by Experiment
ATLAS
CMS

Gridsite

Submitted by sciaba on Wed, 07/17/2013 - 15:13
IPv6 Compliance
Name of Supplier and/or Developer
GridPP
Contact details for Supplier and/or Developer
Andrew McNab
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
More information and/or link(s) to ticket(s)
From Andrew:
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.
Name of Tester
Imperial College
Type
Middleware
Subscribe to Middleware