 |
 |
Ok, I figured out how to disable enough IPv6 on the development machine in order to trick xrootd to being an "ipv4-only" host. I was able to reproduce and confirm the fix works. Basically, Xrootd tries to find a server that can perform the transfer and have some amount of protocol-awareness. By default, it searches for a host that can handle an IPv6 transfer. I changed the default to query for hosts that can do transfers over either IPv4 _or_ IPv6. Now, this assumes that the remote side is compatible with your cluster (i.e., an IPv6-only source will be matched to an IPv4-only cluster ... but a failure obviously still will occur further downstream). It seems the assumption the two side are compatible is better than assuming the remote side is always IPv6-only. @simonmichal - this fix would be very good to backport. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/968#issuecomment-484670799 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1