-
Notifications
You must be signed in to change notification settings - Fork 173
Connecting by a symmetric NAT (still) does not work #321
Comments
I can't tell if it's a symmetric nat problem or not. Your node's IP is not found in the dht when doing a crawl. So it's not even attempting to connect. |
fwiw there are plenty of symmetric nat nodes that are receiving connections.
|
Do you have any suggestions on how we could troubleshoot this? What is odd is that I can favorite people, and I appear in their favorites list, so my traffic seems to go out fine. It is just the incoming traffic that is having problems. |
I am experiencing similar issues. My node is running on a VM in a nat'd virtual network. I can browse, etc, but trying to hit this account's page from my home node results in a timeout/page unavailable status. ob://980f04784695bc4313426be9484caae410a39e0b/store |
Can confirm. I'm using OPNSense (a fork of pfSense) as my firewall, and I could see in the logs that OpenBazaar was reporting Symmetric NAT. And even though the DHT and Hearbeat ports were port forwarded I still got Firewall: Severely restricted. After altering OPNSense to use Full Cone NAT for my OpenBazaar server I get Firewall: Open. |
Connecting via a symmetric NAT (still) does not work.
This issue was previously reported, but erroneously closed: #256
In summary, I can see other peoples pages fine. I can favorite people stores, go to their store, and verify that I am in fact in their favorite list. However, if I try to connect to my page/store from a different location where there are no symmetric NAT issues, the client tells me that the page is offline.
If you would like to verify this, please go to my store, which has zero downtime: 34786ba7b8f3de6f63a3e0bb4e1cf327c9a991bb
Obviously, as my server is behind a symmetric NAT, this will render the upcoming release useless to me. (Otherwise, I think you have done a great job!)
The text was updated successfully, but these errors were encountered: