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
As of DAB Phase 2, there are 2 gossip ServiceEndpoints in the Node.proto. The "internal ip address" is at index 0 and the `external ip address" is at index 1 in the list.
Going forward for the near term, Rosters should have the "external ip address" at index 0 and the platform will only only use the "external" ip address when connecting to peers.
All places where rosters are constructed using node.proto data have the gossip endpoints swapped so that the external ip address is at index 0.
Notes
In the future, the internal IP address will be taken out of the address book and roster to be provided as node configuration. This has not been designed yet, so the data remains as content here in this list.
The text was updated successfully, but these errors were encountered:
Background
As of DAB Phase 2, there are 2 gossip
ServiceEndpoints
in theNode.proto
. The "internal ip address" is at index 0 and the `external ip address" is at index 1 in the list.Going forward for the near term, Rosters should have the "external ip address" at index 0 and the platform will only only use the "external" ip address when connecting to peers.
When constructing Rosters from the node.proto, the order of endpoints needs to be switched so that the external ip address is at index 0.
Acceptance Criteria
All places where rosters are constructed using node.proto data have the gossip endpoints swapped so that the external ip address is at index 0.
Notes
In the future, the internal IP address will be taken out of the address book and roster to be provided as node configuration. This has not been designed yet, so the data remains as content here in this list.
The text was updated successfully, but these errors were encountered: