[quote="Switeck"]
Very similar earlier problem still persists, in part:
index.php/topic,3982.msg23615.html#msg23615
Problem still exists of qBT 3.3.10 trying to listen on the wrong port:
(qBT is set to listen on port 65509)
Launch 1:
12/24/2016 1:56:07 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/65509
12/24/2016 1:56:07 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/65509
12/24/2016 1:56:07 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/37714
12/24/2016 1:56:07 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/37714
12/24/2016 1:56:07 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/65509
12/24/2016 1:56:07 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433
12/24/2016 1:56:07 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/65509
12/24/2016 1:56:06 AM - qBittorrent is trying to listen on any interface port: 65509
12/24/2016 1:56:06 AM - qBittorrent v3.3.10 started
Launch 2:
12/24/2016 3:17:33 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/65509
12/24/2016 3:17:33 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/65509
12/24/2016 3:17:33 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/38632
12/24/2016 3:17:33 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/38632
12/24/2016 3:17:33 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/65509
12/24/2016 3:17:33 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433
12/24/2016 3:17:33 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/65509
12/24/2016 3:17:32 AM - qBittorrent is trying to listen on any interface port: 65509
12/24/2016 3:17:32 AM - qBittorrent v3.3.10 started
Launch 3:
12/24/2016 7:36:50 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/65509
12/24/2016 7:36:50 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/65509
12/24/2016 7:36:50 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/41692
12/24/2016 7:36:50 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/41692
12/24/2016 7:36:50 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/65509
12/24/2016 7:36:50 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433
12/24/2016 7:36:50 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/65509
12/24/2016 7:36:49 AM - qBittorrent is trying to listen on any interface port: 65509
12/24/2016 7:36:49 AM - qBittorrent v3.3.10 started
What is ODD about the choice of port 41692 is qBT also has ESTABLISHED TCP connections on ports 41690 and 41691:
qbittorrent.exe 3788 TCP 127.0.0.1 41691 127.0.0.1 41690 ESTABLISHED
qbittorrent.exe 3788 TCP 127.0.0.1 41690 127.0.0.1 41691 ESTABLISHED
(I spotted this using both TCP View and netstat -n from command prompt/dos box.)
What are these for?[/quote]
Do you see connections to these ports(or connection attempts) to/from external IPs?
[quote="Switeck"]
(Also odd is I didn't see qbittorrent.exe actually listening on port 4433 in TCP View or netstat -n. Is that only used/present if webui is enabled?)
[/quote]
No port 4433 is used by a libtorrent feature called "SSL torrents". It is enabled by default and the 1.0.x series don't give us a way to disable it BEFORE constructing the session. We disable as soon as we construct the session, but libtorrent creates during construction momentarily. The 1.1.x series give us the ability to disabled during session construction and it is never opened.
[quote="Switeck"]
qBitTorrent 3.3.10 32bit version (which uses libtorrent 1.0.10.0) doesn't receive incoming uTP connections. (I tried using multiple other BT clients.)
Deluge 1.3.13, which also uses libtorrent (1.0.9.0), had no problem receiving uTP connections.
Because I was running multiple BitTorrent clients (using different listening ports for each) on the same computer and I checked the firewall settings repeated (as well as deleting firewall entries for qBT and others!)...I conclude this listening bug is in qBT (rather than in libtorrent), possibly related to the same issue that causes the incorrect listening ports in qBT's logger.
qBT could be coaxed into making OUTGOING uTP connections, so I was able to do additional uTP testing...
uTorrent 2.2.1 uploading to qBT 3.3.10 showed ~10% retransmits when using uTP.
uTorrent uploading to Deluge also showed ~10% retransmits when using uTP.
uTorrent uploading to Tixati 2.51 also showed retransmits when using uTP, but closer to 0-1%.
uTorrent uploading to another uTorrent showed a tiny retransmit at start but none after that when using uTP.
Something seems horribly wrong with the implementation of uTP in libtorrent!
[/quote]
Weird, 32bit version uses the exact same version of libtorrent as the 64bit one. I don't know why utp fails. Does DHT work ok? (both are based on udp).