Skip to content
This repository has been archived by the owner on May 11, 2022. It is now read-only.

Use traceroute to determine if an AutoNAT server is acceptable #46

Open
Stebalien opened this issue Feb 25, 2020 · 4 comments
Open

Use traceroute to determine if an AutoNAT server is acceptable #46

Stebalien opened this issue Feb 25, 2020 · 4 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@Stebalien
Copy link
Member

We should consider using some form of traceroute on IPv6 to determine if a potential AutoNAT server is viable. This should be very fast because we just want to verify that we hit some public IP on the route.

If we can get this working correctly, we can skip the other heuristics (although some of them may be a good initial check).

@Stebalien
Copy link
Member Author

Yeah, it looks like we may be able to do a UDP simple UDP traceroute. We're not trying to get all the way to the target, just out of our network.

@willscott
Copy link
Contributor

They'll all be "public" IPs, so we'll need some heuristic for deciding that we've hit some router along the way with an IP that diverges significantly from those of the endpoints.

Could we get away in many cases with just latency as an estimator of being in the same network?

@Stebalien
Copy link
Member Author

Ah, because IPv6... Actually, we there's no reason not to try IPv4, right (if the peer has an IPv4 address)?

@Stebalien
Copy link
Member Author

Could we get away in many cases with just latency as an estimator of being in the same network?

Maybe? But I'd want to set that limit to be really short (like 1-5ms).

@willscott willscott added the kind/enhancement A net-new feature or improvement to an existing feature label Mar 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants