Skip to content
This repository has been archived by the owner on May 16, 2019. It is now read-only.

Connecting by a symmetric NAT (still) does not work #321

Open
lunokhod opened this issue Apr 1, 2016 · 5 comments
Open

Connecting by a symmetric NAT (still) does not work #321

lunokhod opened this issue Apr 1, 2016 · 5 comments

Comments

@lunokhod
Copy link

lunokhod commented Apr 1, 2016

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!)

@cpacia
Copy link
Member

cpacia commented Apr 1, 2016

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.

@cpacia
Copy link
Member

cpacia commented Apr 1, 2016

fwiw there are plenty of symmetric nat nodes that are receiving connections.

received response for message id bB8/NuHQ3Sp2SNlDh9j22gNU7Ho= from 88.150.242.119:49775, NAT=SYMMETRIC, relay=(u'91.121.75.30', 28467)

@lunokhod
Copy link
Author

lunokhod commented Apr 3, 2016

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.

@JulianTosh
Copy link

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

@kabo
Copy link

kabo commented Jun 2, 2017

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.

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

4 participants