Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

Sometimes the transport_tcp listener doesn't see a discovered_nat message #357

Open
Vagabond opened this issue Jun 18, 2021 · 2 comments
Open

Comments

@Vagabond
Copy link
Contributor

When a NAT is discovered, the nat server sends the transport listener a nat_discovered message. Sometimes, however, the message is not received. I do not know why this is.

@wolasss
Copy link

wolasss commented Aug 13, 2021

@Vagabond Could this be a reason why p2p connection fails with timeout?

@Vagabond
Copy link
Contributor Author

No, that's likely due to a routing failure, the target being too busy or a stale peerbook.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants