Skip to content

behindFirewall option #1692

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.

Sign up for GitHub

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

Draft
the-headless-ghost wants to merge 1 commit into
base: staging
Choose a base branch
from
Draft

behindFirewall option #1692

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/get-started/infrastructure/node/topology.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,7 @@ A minimal version of this file looks like this:
"valency": 1,
"warmValency": 2,
"trustable": true,
"behindFirewall": false,
"diffusionMode": "InitiatorAndResponder"
}
],
Expand Down Expand Up @@ -110,6 +111,9 @@ A minimal version of this file looks like this:
Local permission corresponds to the value of the advertise parameter.
On the other hand, 'remote permission' is tied to the `PeerSharing` value associated with the remote address, which is ascertained after the initial handshake between nodes.

* The `behindFirewall` is an optional field.
If activated, the node will not attempt to initiate outbound connections to the specified peers.
Instead, it will wait for the peers behind a firewall to establish the connection.

* Local root groups shall be non-overlapping.

Expand Down
Loading