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 Apr 7, 2022. It is now read-only.
When assigning a new IP to an Orion node (let's say Node A), which has already established connections with other orion nodes (Node B, Node C) with mutual authentication, then the communication does not succeeds when the updating process of the orion_ca.pem file in the other orion nodes (Nodes "B" and "C") is not totally made.
For instance, let's say that only node "B" updates its orion.conf file with the new Node "A" IP address; In that case communication between "A" and "B" won't succeed because node "C" still advertises the old IP address of node "A".
The only way I found as a workaround is that all other nodes ("B" and "C") should update their orion.conf file.
This issue has a huge impact especially in scenarios where lots of orion nodes have complex interactions.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When assigning a new IP to an Orion node (let's say Node A), which has already established connections with other orion nodes (Node B, Node C) with mutual authentication, then the communication does not succeeds when the updating process of the orion_ca.pem file in the other orion nodes (Nodes "B" and "C") is not totally made.
For instance, let's say that only node "B" updates its orion.conf file with the new Node "A" IP address; In that case communication between "A" and "B" won't succeed because node "C" still advertises the old IP address of node "A".
The only way I found as a workaround is that all other nodes ("B" and "C") should update their orion.conf file.
This issue has a huge impact especially in scenarios where lots of orion nodes have complex interactions.
The text was updated successfully, but these errors were encountered: