-
Notifications
You must be signed in to change notification settings - Fork 252
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
Document ports requirements #22
Comments
Yes, default port for bitcoin-like network is 28333 (tcp). This will be requested to your upnp-aware router if you compiled miniupnp support. Default port to DHT and torrent is 28333 + 1000 = 29333 (both udp and tcp). afair libtorrent will also try to upnp request it. |
I noticed many more ports opened by twister, namely 4433, 4434, 1900. It would be great to document these (and the above) in the official documentation. |
@BlockTester +1 |
@BlockTester @iShift Miguel said elsewhere that 4433-4 are likely for the RPC interface over SSL (which might not work, at this point) inherited from bitcoind, since he himself didn't use them. I have them blocked in my AWS instance and things seem to work ok anyway. Haven't seen 1900 before though... |
Ok, I've figured it out. 4433 is the default LIBTORRENT ssl port, i.e. for DHT operations only. Because @miguelfreitas expects 29333 in code, I believe that other port is just sitting there doing nothing...? Wrapping up, @eschnou : if you want to document this anywhere:
|
|
Weird, I don't see 1900 and 60177 here on OSX...? What's the exact command you ran ? |
For listing?
Running Debian Jessie/Testing 64bit. |
@toyg just to confirm: 4433 is from libtorrent (not sure if used for DHT or torrent though) not bitcoin's. Bitcoin's inherited SSL RPC support is believed to work, but untested. |
@BlockTester ok, yes, I see it now:
SSDP sits on port 1900. http://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol I don't see port 60177 but I do have a couple of random-looking UDP listening in the ephemeral range. I suspect it's more UPNP stuff. |
Good find for the port, I honest hadn't even searched. Nevertheless it should be documented since the program does indeed open that port. Likewise for the rest of the UPNP stuff. Is there a switch somewhere to turn it off altogether? I suspect most people at this stage don't even use it (when more regular joes will join in that might be a different story). |
man, I love upnp, it's a life-saver! 😸 You can disable it in twister.conf with |
old issue we can close that we have pull #121 |
Should any ports be available to the outside for proper operation of the daemon? Does it help the network if we open some ports? I could not find documentation about this anywhere.
The text was updated successfully, but these errors were encountered: