XROOTD-L Archives

Support use of xrootd by HEP experiments

XROOTD-L@LISTSERV.SLAC.STANFORD.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ulf Tigerstedt <[log in to unmask]>
Reply To:
Support use of xrootd by HEP experiments <[log in to unmask]>
Date:
Tue, 27 May 2014 23:01:53 +0300
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
Hello!

We (at NDGF-T1) are trying to be ahead of demand and are testing dCache 
as an IPv6 xrootd-server... but it's not going very well.

http://xrootd.org/doc/dev4/XRdv300.htm#_Toc372751539 says that the node 
response should look like:

xy[::aaa.bbb.ccc.ddd.eee]:ppppp

Giving the xrdfs client an IPv6 answer like
Sw[::2001:948:40:2:0:0:0:149]:1094  causes the client to sputter out 
"Invalid address" and refuses to work.

When testing xrdfs against an xrootd daemon over IPv6, the answer is a 
bit sad:
Sw[::193.166.0.114]:1094   = the machine handshakes over IPv6, then 
switches to IPv4 for everything else.

What is an IPv6 response supposed to look like, really?
Or is the IPv6 for xrootd4 just "IPv6", usable for handshaking but not 
really usable?

(I'm also involved in the HEPIX IPv6 working group, so we are testing 
all protocols we can find to see which of them really works with IPv6)

//Tiggi, NDGF-T1

-- 
Ulf Tigerstedt || CSC Oy || NDGF
Computing Environments group
(NGI_FI and NGI_NDGF) deputy manager
GSM +358503818558 || +35894572279
Keilaranta 14 || Espoo || Finland

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1

ATOM RSS1 RSS2