VS Code Server downloads fail through Hurricane Electric tunnelbroker IPv6 Ranges.

It appears that VSCode downloads occurring over a Hurricane Electric Tunnel Broker v6 range is blocked in some form or fashion at the CDN level.

When manually wget'ing the relevant files forcing IPv4 connectivity everything works as expected.

From a network connectivity standpoint the v6 tunnel is working as expected with the exception of downloads for vscode server and extensions. This is not a network issue from our end as we can see successful connections when performing ICMP Pings to the endpoint so routing is in place, and we don't have any deny statements for outbound traffic. We are receiving Server TCP Resets not Client TCP Resets. This is indicative of some kind of policy enforcement point acting against my allocated v6 range.

I am not sure if there is anything that can be done from a github issue or if this needs to be worked on at a different level. But it is certainly a nuisance as my ISP does not provide IPv6 connectivity and as a network engineer for my job I require IPv6 leaving tunnelbroker as my only option.

No repository file or test is identified. Start by reproducing VS Code Server and extension downloads over the Hurricane Electric Tunnel Broker IPv6 range, then compare them with forced IPv4 downloads and the reported server TCP resets. Done requires a confirmed repository-side fix or evidence that the issue must be handled outside this repository.