Using my own compiled exes of cfpp2p's transmission "branch" for cygwin.
Well, what can I say. So far it's stable and fast. *thumbs up*
Search found 3 matches
- Thu Nov 07, 2013 3:32 pm
- Forum: General
- Topic: daemon for windows
- Replies: 12
- Views: 19952
- Mon Apr 08, 2013 11:30 am
- Forum: Support
- Topic: Tranmission ports?
- Replies: 2
- Views: 3094
Re: Tranmission ports?
Each peer connected gets their own local port which is assigned by the OS.
With TCP yes, but UDP is connectionless so no these are not "connected" peers. Also, netstat showed 0.0.0.0:* as remote address for those udp ports/sockets.
I of course didn't post TCP sockets that belong to peer ...
With TCP yes, but UDP is connectionless so no these are not "connected" peers. Also, netstat showed 0.0.0.0:* as remote address for those udp ports/sockets.
I of course didn't post TCP sockets that belong to peer ...
- Sun Apr 07, 2013 6:36 pm
- Forum: Support
- Topic: Tranmission ports?
- Replies: 2
- Views: 3094
Tranmission ports?
Hey,
I'm running Transmission daemon version 2.77 and I'm wondering about the ports / sockets it binds:
to control the daemon:
tcp 127.0.0.1:9091
bittorrent ports:
tcp 0.0.0.0:51413
tcp6 :::51413
udp 0.0.0.0:51413
First curious thing: where's udp6 for port 51413?
More ports, what's their ...
I'm running Transmission daemon version 2.77 and I'm wondering about the ports / sockets it binds:
to control the daemon:
tcp 127.0.0.1:9091
bittorrent ports:
tcp 0.0.0.0:51413
tcp6 :::51413
udp 0.0.0.0:51413
First curious thing: where's udp6 for port 51413?
More ports, what's their ...