Middleware

Enstore

Submitted by flopez on
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
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
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

xrootd

Submitted by sciaba on
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.

Hadoop

Submitted by sciaba on
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
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

StoRM

Submitted by sciaba on
IPv6 Compliance
Name of Supplier and/or Developer
EMI
Version
1.11.11
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
More information and/or link(s) to ticket(s)
The SRM server does not bind to the IPv6 address by default. The solution is to add to the property storm.service.SURL.endpoint of /etc/storm/backend-server/storm.properties the SRM endpoint with its IPv6 address. For more information, see

https://issues.infn.it/jira/browse/STOR-457
https://ggus.eu/index.php?mode=ticket_info&ticket_id=99461
Type
Middleware
Used by Experiment
ALICE
ATLAS
CMS
LHCb

ARGUS

Submitted by sciaba on
IPv6 Compliance
Name of Supplier and/or Developer
EMI
Does developer claim IPv6 compliance?
Yes
More information and/or link(s) to ticket(s)
https://ggus.eu/index.php?mode=ticket_info&ticket_id=124315
Type
Middleware
Used by Experiment
ALICE
ATLAS
CMS
LHCb

ARC CE

Submitted by sciaba on
IPv6 Compliance
Name of Supplier and/or Developer
EMI
Does developer claim IPv6 compliance?
Yes
More information and/or link(s) to ticket(s)
Reported to work on IPv6 by Duncan Rand.
Type
Middleware
Used by Experiment
ATLAS
CMS

glideinWMS

Submitted by sciaba on
IPv6 Compliance
Name of Supplier and/or Developer
OSG
Contact details for Supplier and/or Developer
Igor Sfiligoi
Does developer claim IPv6 compliance?
Yes
Did you try running on dual stack system?
No
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?
Don't know/not tested
More information and/or link(s) to ticket(s)
glideinWMS uses Condor for all network activities. Therefore it should have the same level of IPv6 compliance, though it has never been tested.
Type
Middleware
Used by Experiment
CMS
Subscribe to Middleware