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, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@bbockelm in #968: 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.\r\n\r\nBasically, 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.\r\n\r\nNow, 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.\r\n\r\n@simonmichal - this fix would be very good to backport."}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/968#issuecomment-484670799"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/968#issuecomment-484670799",
"url": "https://github.com/xrootd/xrootd/issues/968#issuecomment-484670799",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
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
