-
Notifications
You must be signed in to change notification settings - Fork 86
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.
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
NonP2P relays fail to keep an established connection to a P2P node #4465
Labels
bug
Something isn't working
Comments
Thanks @Straightpool, this fits quite well with IOG & CF investigation. We're colaborating on a fix. |
coot
added a commit
to IntersectMBO/cardano-node
that referenced
this issue
Mar 23, 2023
Includes fix for IntersectMBO/ouroboros-network#4465.
coot
added a commit
to IntersectMBO/cardano-node
that referenced
this issue
Mar 24, 2023
Includes fix for IntersectMBO/ouroboros-network#4465.
coot
added a commit
to IntersectMBO/cardano-node
that referenced
this issue
Mar 24, 2023
Includes fix for IntersectMBO/ouroboros-network#4465.
coot
added a commit
to IntersectMBO/cardano-node
that referenced
this issue
Mar 24, 2023
Includes fix for IntersectMBO/ouroboros-network#4465.
coot
added a commit
to IntersectMBO/cardano-node
that referenced
this issue
Mar 24, 2023
Includes fix for IntersectMBO/ouroboros-network#4465.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After
1.35.6
release ofcardano-node
, we received some reports where BPs weren't able to keep an established connection to a P2P node.@karknu was able to reproduce the issue and capture a
pcap
trace, this was interpreted to create the following diagram (where BP is assumed to be a non P2P node):We believe this is a bug in the legacy non-p2p code, which is triggered by P2P nodes which bind to their advertised addressed for outbound connections. The non-p2p component which tracks the state of inbound & outbound connections can be confused by this and depending on which nodes connects first (e.g.
P2P -> NonP2P
orNonP2P -> P2P
) this can either result in minutes long or hour long (or more) problems for a non-p2p node to establish a connection to a p2p node.The text was updated successfully, but these errors were encountered: