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
1 kubo go-libp2p peer behind NAT with a circuit relay 2 reservation over QUIC
circuit relay v2 peer
Holepunching take just over 5 seconds even though the latency between the peers is no more than 150ms.
This problem was observed in the VoleCheckBitswapCID method.
Due to a context deadline shorter than the ~5 seconds it takes for the hole punching to succeed, that is defined in the Boxo Bitswap implementation, a workaround was added to open a stream before with a longer deadline. Below are debug logs showing the connection succeeding using this approach after a little over 5 seconds.
What's wrong
Given the following scenario:
Holepunching take just over 5 seconds even though the latency between the peers is no more than 150ms.
This problem was observed in the Vole
CheckBitswapCID
method.Due to a context deadline shorter than the ~5 seconds it takes for the hole punching to succeed, that is defined in the Boxo Bitswap implementation, a workaround was added to open a stream before with a longer deadline. Below are debug logs showing the connection succeeding using this approach after a little over 5 seconds.
logs
Below are the logs from a feature branch of Vole, whereby we open a stream right after opening the connection to force hole punching
The text was updated successfully, but these errors were encountered: