You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
We need to have the wsPort of a node expose to the outside world.
Motivation
One may want to add a reputable node as a fixed peers, the wsPort is required for that.
In a cluster all nodes may have the same public ip. This causes an issue with the lisk p2p system because all peers are referenced with their public ip & port. So when running several nodes behind the same public ip, we must use different ports in order to not be referenced as duplicate connection among peers. To be able to use different ports, we must know what ports are currently in use, hence the need for that to be exposed by the node.
Acceptance Criteria
network.port must be exposed publicly
The text was updated successfully, but these errors were encountered:
Description
We need to have the
wsPort
of a node expose to the outside world.Motivation
One may want to add a reputable node as a fixed peers, the
wsPort
is required for that.In a cluster all nodes may have the same public ip. This causes an issue with the lisk p2p system because all peers are referenced with their public ip & port. So when running several nodes behind the same public ip, we must use different ports in order to not be referenced as duplicate connection among peers. To be able to use different ports, we must know what ports are currently in use, hence the need for that to be exposed by the node.
Acceptance Criteria
network.port
must be exposed publiclyThe text was updated successfully, but these errors were encountered: