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
👍 if you often can't find other peers behind NAT/firewall, while using WAN mode, with your node also behind NAT/firewall. This problem seems to appear after the ipfs-network upgraded to circuit-relay v2. The local node behind NAT/firewall doesn't seem to get a /p2p-circuit/ multiaddress for a long time.
Also, even when two publicly undiallable nodes share the same pubsub peers, messagaing between them through gossipsub is extremely slow if all those peers are not subscribed to the same chatroom topic.
The text was updated successfully, but these errors were encountered:
👍 if you often can't find other peers behind NAT/firewall, while using WAN mode, with your node also behind NAT/firewall. This problem seems to appear after the ipfs-network upgraded to circuit-relay v2. The local node behind NAT/firewall doesn't seem to get a
/p2p-circuit/
multiaddress for a long time.Also, even when two publicly undiallable nodes share the same pubsub peers, messagaing between them through gossipsub is extremely slow if all those peers are not subscribed to the same chatroom topic.
The text was updated successfully, but these errors were encountered: