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
This issue is a more scoped subset of the problems described in #2965.
The hole punching code doesn't use the addresses from the Libp2p host. Instead it only uses the observed addresses from Identify, and the addresses of the network interfaces.
Actually the "server" and the "client" parts of hole punching don't use the same set of addresses, as seen in the following code fragments:
I suggest to use host.Addrs() directly in both places, as those includes all the possible addresses, including the ones provided by the custom AddrsFactory.
The text was updated successfully, but these errors were encountered:
This issue is a more scoped subset of the problems described in #2965.
The hole punching code doesn't use the addresses from the Libp2p host. Instead it only uses the observed addresses from Identify, and the addresses of the network interfaces.
Actually the "server" and the "client" parts of hole punching don't use the same set of addresses, as seen in the following code fragments:
go-libp2p/p2p/protocol/holepunch/svc.go
Lines 279 to 307 in 921cc71
go-libp2p/p2p/protocol/holepunch/holepuncher.go
Line 209 in 921cc71
I suggest to use
host.Addrs()
directly in both places, as those includes all the possible addresses, including the ones provided by the custom AddrsFactory.The text was updated successfully, but these errors were encountered: