Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: autoNAT unknown -> public -> private #111

Open
erhant opened this issue Aug 29, 2024 · 0 comments
Open

bug: autoNAT unknown -> public -> private #111

erhant opened this issue Aug 29, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@erhant
Copy link
Member

erhant commented Aug 29, 2024

AutoNAT usually decides on the status at the start after a few seconds, most of the time its Unknown to Private

In a random run this happened:

  1. As usual, decided that its private
[2024-08-29T13:42:45.074Z WARN  dkn_compute::p2p::client] AutoNAT status changed from Unknown to Private
  1. After sometime, decided that its public:
[2024-08-29T13:50:17.374Z WARN  dkn_compute::p2p::client] AutoNAT status changed from Private to Public("/ip4/192.168.1.37/tcp/4001/p2p/16Uiu2HAm7EtCPAh8TiXbooEdcbi9nxUEYhzpgw2UvfeoaDB8vZhp")
  1. Then, it went back to private:
[2024-08-29T13:51:56.985Z WARN  dkn_compute::p2p::client] AutoNAT status changed from Public("/ip4/192.168.1.37/tcp/4001/p2p/16Uiu2HAm7EtCPAh8TiXbooEdcbi9nxUEYhzpgw2UvfeoaDB8vZhp") to Private

Worth noting & explaining why this happens.

@erhant erhant added the bug Something isn't working label Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant