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

fix(iroh-net): Fix in detecting globally routable IPv6 addresses #2030

Merged
merged 4 commits into from
Feb 19, 2024

Conversation

flub
Copy link
Contributor

@flub flub commented Feb 16, 2024

Description

We were incorrectly identifying globally routable IPv6 addresses as
not routable. This make netcheck skip IPv6 addresses.

Notes & open questions

Closes #2022

The fix in the netcheck, test is curious, it fails on this PR fairly
consistently yet it is really a flaky test introduced in combination with #2027.
Now that we have IPv6 resolving properly we might get an IPv6 result. Since
this test only has a single DerpUrl it only needs one result to complete.
This could be an IPv4 OR an IPv6 result, we don't know which one will be
faster. And if the other is slow enough then it won't be received. I think
this behaviour is fine, we simply can't guarantee that both must have a result
and the point of netcheck is to return something working quickly.

Change checklist

  • Self-review.
  • Documentation updates if relevant.
  • Tests if relevant.

We were incorrectly identifying globally routable IPv6 addresses as
not routable.  This make netcheck skip IPv6 addresses.
@dignifiedquire dignifiedquire added this to the v0.13.0 milestone Feb 19, 2024
@flub flub added this pull request to the merge queue Feb 19, 2024
Merged via the queue into main with commit c3aa17e Feb 19, 2024
23 checks passed
@flub flub deleted the flub/ipv6-routable-mask branch February 19, 2024 13:22
fubuloubu pushed a commit to ApeWorX/iroh that referenced this pull request Feb 21, 2024
…computer#2030)

## Description

We were incorrectly identifying globally routable IPv6 addresses as
not routable.  This make netcheck skip IPv6 addresses.

## Notes & open questions

Closes n0-computer#2022 

The fix in the netcheck, test is curious, it fails on this PR fairly
consistently yet it is really a flaky test introduced in combination
with n0-computer#2027.
Now that we have IPv6 resolving properly we might get an IPv6 result.
Since
this test only has a single DerpUrl it only needs one result to
complete.
This could be an IPv4 OR an IPv6 result, we don't know which one will be
faster. And if the other is slow enough then it won't be received. I
think
this behaviour is fine, we simply can't guarantee that both must have a
result
and the point of netcheck is to return something working quickly.

## Change checklist

- [x] Self-review.
- [x] Documentation updates if relevant.
- [x] Tests if relevant.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Netcheck fails to find working IPv6 connection
2 participants