-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Users can reliably connect to the network via UPnP #312
Comments
@ManfredKarrer, I've updated the title and description here. I've dropped any mention of manual port forwarding, because we know that works. I think this user story is really about ensuring that the maximum number of users possible can connect automatically via UPnP. Sound OK to you? |
UPnP behaves pretty strange. I tried it with 2 different routers (same brand, diff model) and both work sometimes and sometimes not. I have not found yet clear patterns. We should investigate the weupnp library used inside TomP2P and cross check it with alternative UPnP implementations. |
Closed as related to TomP2P which is not used anymore. |
Currently about half of Bitsquare must set port forwarding manually within their routers. For the other half, UPnP (universal plug-and-play) works, and automatically establishes port forwarding on their behalf.
See #305, which deals specifically with understanding and solving these UPnP problems; the ultimate goal is that all Bitsquare users are able to automatically and reliably connect to the Bitsquare network without any manual setup. It should be as easy as working with Skype, for example.
The text was updated successfully, but these errors were encountered: