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
In this screenshot you can see that two routes (g.solstice and g.phobos) are extremely long and go through many nodes that exist elsewhere in the routing table. Pinging either of these destinations leads to a timeout.
It seems like the connector should be able to clean up these stale routes, or at least not rebroadcast them to its peers.
The text was updated successfully, but these errors were encountered:
In this screenshot you can see that two routes (
g.solstice
andg.phobos
) are extremely long and go through many nodes that exist elsewhere in the routing table. Pinging either of these destinations leads to a timeout.It seems like the connector should be able to clean up these stale routes, or at least not rebroadcast them to its peers.
The text was updated successfully, but these errors were encountered: