Improve experience with NAT'ed/Firewalled peers #614
Labels
exp/wizard
Extensive knowledge (implications, ramifications) required
P1
High: Likely tackled by core team if no one steps up
status/in-progress
In progress
hsanjuan commentedDec 7, 2018
•
edited
Basic information
Description
Since we enabled DHT discovery we stopped manually opening connections to every peer when joining (which was a mess). A downside is that a firewalled peer can only join by talking directly to the leader and in some cases, by manually opening connections to the rest of peers in the cluster.
We should:
is needed. In this case, it should enable any peer to reach firewalled peers through the peer it first contacted.
The scenario that should work is 2 peers online, reachable on the internet, and peers behind NAT or with incoming ports filtered should be able to join the cluster, and be reached by any other peer in it (even other firewalled peers on different networks).
The text was updated successfully, but these errors were encountered: