 |
 |
On 27/05/14 23:29, Lukasz Janyst wrote: > On 27/05/14 22:21, Lukasz Janyst wrote: >>> 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. >> >> Most of the requests handled by xrdfs either redirect or use locate >> queries and the client goes to a host it is pointed to. It switched to >> IPv4 because the server told it to do so. > > Sw[::193.166.0.114]:1094 in fact is server's answer to a kXR_locate > request. So what you likely did was asking for a directory listing. This > triggered a kXR_locate request and you dCache server told the client to > go to [::193.166.0.114]:1094 over IPv4 which the client did. What you > see is a dCache bug, not xrootd. 193.166.0.114 is a dualstacked box running xrootd 4.0.0rc3 (It's actually my testbox against dcache). It is running the xrootd daemon from 4.0.0rc3 to have something to compare dcache to. -- 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