Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Server 2022 runner does not have IPv6 connectivity #9401

Closed
4 of 13 tasks
jozefizso opened this issue Feb 24, 2024 · 5 comments
Closed
4 of 13 tasks

Windows Server 2022 runner does not have IPv6 connectivity #9401

jozefizso opened this issue Feb 24, 2024 · 5 comments

Comments

@jozefizso
Copy link

Description

GitHub hosted cloud runners with Windows Server are not able to communicate with IPv6 hosts.

IPv6 was introduced on December 1995, 28 years ago. We should be able to use it in workflows.

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 11
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

Current runner version: '2.313.0'
Operating System
Microsoft Windows Server 2022
10.0.20348
Datacenter
Runner Image
Image: windows-2022
Version: 20240218.2.0
Included Software: https://github.com/actions/runner-images/blob/win22/20240218.2/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20240218.2

Is it regression?

no

Expected behavior

I can be able to connect to IPv6 hosts.

Actual behavior

Cloud runners are able to connect to IPv6 hosts.

Repro steps

Run this command on Windows Server runners:

curl -m 3 -6 https://ifconfig.co/

The curl will fail with error curl: (6) Could not resolve host ifconfig.co.

@mikhailkoliada
Copy link
Contributor

Duplicte of #668

@jozefizso
Copy link
Author

Hi @mikhailkoliada, I hope you are doing well.

GitHub hosted cloud runners with Windows Server are not able to communicate with IPv6 hosts.
IPv6 was introduced on December 1995, 28 years ago. We should be able to use it in workflows.

This issue was not answered.

@mikhailkoliada
Copy link
Contributor

@jozefizso hey, we do not support ipv6 for both inbound or outbound ways, so it is expected

@jozefizso
Copy link
Author

jozefizso commented Feb 25, 2024

@mikhailkoliada This is not expected for a networking technology which is 28 years old in a world where servers are accessible using IPv6.

@jozefizso
Copy link
Author

IPv6 is the actual internet protocol, while IPv4 is a legacy protocol. Please, priorize this request.

https://github.com/orgs/community/discussions/10539#discussioncomment-2063601

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants