-
Notifications
You must be signed in to change notification settings - Fork 288
fix: wait for at least one ipv6 and ipv4 qad report #3413
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
Conversation
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/3413/docs/iroh/ Last updated: 2025-07-29T13:41:25Z |
We also have |
This will increase the time the report takes, because now it might take a run across the ocean. I don't know enough how relevant that is, so not sure what the right call is here - will defer to others or need to dig in further first. |
that’s not needed, we only need at least two ipv4 or two ipv6 and only if we have a least two relays |
Co-authored-by: Philipp Krüger <[email protected]>
So much confidence in that statement... 😁 |
Description
If an endpoint only has a single relay URL configured in its relay map, we currently abort the QAD net reports after a single successful report. However, we also decide whether an endpoint supports IPv6 on the fact if a QAD IPv6 report completed successfully or not. Those are two reports though, and if we abort after the first one, we falsely assume that the endpoint has no IPv6 connectivity.
This PR changes this in a rather simple way: If we did start both IPv4 and IPv6 reports, we always wait at least until one of each completed.
Unrelated to this change, the PR also adds logging when the best address changes.
Breaking Changes
Notes & open questions
Change checklist
quic-rpc
iroh-gossip
iroh-blobs
dumbpipe
sendme