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
I'm trying to observe the establishment of a connection from relayed to direct (using DCuTR).
Initially I thought that I could use the Connectedness' Limited state for that. This works find when using a limited relay, but it fails for an unlimited relay:
A connection via an unlimited relay is considered Connected right away, and the establishment of a direct (hole-punched) connection doesn't trigger another event, since we're already "connected".
The best resolution I could come up with is the following: Split the Limited state into two: Relayed and RelayedUnlimited. This is a breaking change obviously, but at it's made explicit by the removal of Limited, forcing users of the library to rethink their logic.
The text was updated successfully, but these errors were encountered:
I'm trying to observe the establishment of a connection from relayed to direct (using DCuTR).
Initially I thought that I could use the
Connectedness
'Limited
state for that. This works find when using a limited relay, but it fails for an unlimited relay:go-libp2p/p2p/protocol/circuitv2/client/dial.go
Lines 181 to 182 in 4e85c96
A connection via an unlimited relay is considered
Connected
right away, and the establishment of a direct (hole-punched) connection doesn't trigger another event, since we're already "connected".The best resolution I could come up with is the following: Split the
Limited
state into two:Relayed
andRelayedUnlimited
. This is a breaking change obviously, but at it's made explicit by the removal ofLimited
, forcing users of the library to rethink their logic.The text was updated successfully, but these errors were encountered: