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

Turn on even if we might be behind a NAT #73

Closed
Stebalien opened this issue Apr 7, 2020 · 1 comment · Fixed by #75
Closed

Turn on even if we might be behind a NAT #73

Stebalien opened this issue Apr 7, 2020 · 1 comment · Fixed by #75
Assignees

Comments

@Stebalien
Copy link
Member

We added a feature to only turn on if another AutoNAT node tells us we're not behind a NAT. Unfortunately, this makes it painful to bootstrap a network.

The original motivation was that we didn't want a cluster of nodes behind the same firewall to determine that they're all reachable. However, I'm not sure if that's actually effective. All it takes is for a single node to be reachable for the entire cluster to say "I'm reachable!".

Instead, we should probably just implement #47.

@willscott
Copy link
Contributor

A potentially complementary approach to the point mentioned here is that it could be useful for nodes to be running the autonat service in at least a limited level until they they begin to believe they are in a private situation.

Currently, there are anticipated issues with a private network bootstrapping correctly, because no nodes will initially be running an autonat service in their default auto-detect mode.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants