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

IPv6 support #447

Open
6 of 10 tasks
MartinKolarik opened this issue Nov 25, 2023 · 0 comments · May be fixed by #522
Open
6 of 10 tasks

IPv6 support #447

MartinKolarik opened this issue Nov 25, 2023 · 0 comments · May be fixed by #522
Assignees

Comments

@MartinKolarik
Copy link
Member

MartinKolarik commented Nov 25, 2023

I'm opening this to track the requirements for IPv6 support.

Targeting IPv6-enabled hosts in tests:

  • Being able to specify IPv6 address in all relevant inputs.
    • This must automatically filter the probes to only those that do support IPv6 (and IPv4 addresses must filter to those that support IPv4)
    • On the probe side, we need to test the output parsing for each test type.
  • When a domain is specified, there must be a way to choose the connection type: auto/ipv4/ipv6.
    • TBD: Do we auto-select the probes based on this, or do we add tags visible to users?
  • The anti-abuse system must support IPv6.

Probes running in dual-stack and IPv6-only networks:

  • Probes detect which connection types they support for tests and report this to the API.
  • There is only one connection to the API via either IPv4/IPv6. The selection is up to the probe. This doesn't affect the user's ability to run tests of the other type.
  • Infrastructure: The LB and/or API must accept IPv6 connections.
  • Infrastructure: The probe update system (both docker and code) must accept IPv6 connections.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant