It seems the assumption the two side are compatible is better than assuming the remote side is always IPv6-only.
That's for sure the case, IPv6-only is still rare, but dual-stack vs. IPv4-only is pretty common. And I hope that IPv4 only will die out earlier than IPv6 only arises, at least for us this will be true 😉.
Many thanks for the fix and explanation!
This would indeed surely be a good backport candidate. While IPv4-only servers are becoming more rare nowadays, our example shows they still exist. In case people are curious (that's now of course off-topic!): Our main blocker preventing IPv6 introduction is a controllable DHCPv6 workflow. Many clients don't play well with DHCPv6 (e.g. client-id changing especially when installing a machine via PXE) and we don't want to go down the routes of full autoconfiguration or full static configuration (both would be easy in straightforward, but come at a price).
—
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":"@olifre in #968: \u003e It seems the assumption the two side are compatible is better than assuming the remote side is always IPv6-only.\r\n\r\nThat's for sure the case, IPv6-only is still rare, but dual-stack vs. IPv4-only is pretty common. And I hope that IPv4 only will die out earlier than IPv6 only arises, at least for us this will be true :wink:. \r\n\r\nMany thanks for the fix and explanation! \r\nThis would indeed surely be a good backport candidate. While IPv4-only servers are becoming more rare nowadays, our example shows they still exist. In case people are curious (that's now of course off-topic!): Our main blocker preventing IPv6 introduction is a controllable DHCPv6 workflow. Many clients don't play well with DHCPv6 (e.g. client-id changing especially when installing a machine via PXE) and we don't want to go down the routes of full autoconfiguration or full static configuration (both would be easy in straightforward, but come at a price). "}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/968#issuecomment-484677398"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/968#issuecomment-484677398",
"url": "https://github.com/xrootd/xrootd/issues/968#issuecomment-484677398",
"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