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

AutoNAT: Network ReachabilityPublic distinguishes between IPv6 and IPv4 #614

Closed
wlynxg opened this issue May 14, 2024 · 2 comments · May be fixed by #538
Closed

AutoNAT: Network ReachabilityPublic distinguishes between IPv6 and IPv4 #614

wlynxg opened this issue May 14, 2024 · 2 comments · May be fixed by #538

Comments

@wlynxg
Copy link

wlynxg commented May 14, 2024

Currently, AutoNAT considers the node to be in the public state as long as one address can be dialed successfully, but it does not differentiate between address types.

For example, when the IPv6 address of node A is Public but the IPv4 address is private, node A will think that its network is ReachabilityPublic. The ReachabilityPublic state will prevent node A from connecting to Relay. However, when another node is in an IPv4-only network environment, it will be unable to connect to node A because there is no Relay connection.

Is it possible to consider subdividing the node Network Reachability into ReachabilityIPv4Public, ReachabilityIPv6Public and ReachabilityPublic (including IPv4 and IPv6)? I think more detailed address visibility differentiation will allow developers to formulate strategies in more detail.

@MarcoPolo
Copy link
Contributor

Will be fixed in Autonat V2 #538

@MarcoPolo MarcoPolo linked a pull request Jun 19, 2024 that will close this issue
@dhuseby
Copy link

dhuseby commented Jul 2, 2024

@wlynxg it looks like this is addressed in the autonat spec, if you have any more questions, feel free to re-open this issue

@dhuseby dhuseby closed this as completed Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants