You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running libtorrent 0.13.8 with rtorrent 0.9.8 - noticed that rTorrent on server was unable to connect to a torrent client running on my local computer and decided to investigate the logs.
More strangely, while some of incoming connection attempts end up with network error, some others connect successfully "Handshake success". No pattern could be spotted between successful and failing ones.
Collected a pcap of both sides (my local machine and server) but could not spot anything unusual. After the Handshake, which is received without issues, server sends a FIN packet in order to close the connection.
Changing the network connection (used tethered 4G) made it to work - but again, connection between the two machines is solid.
Any guidance on how to proceed? Any way of increasing logging for handshake_manager beyond just a "network error"?
Thanks!
The text was updated successfully, but these errors were encountered:
Running libtorrent 0.13.8 with rtorrent 0.9.8 - noticed that rTorrent on server was unable to connect to a torrent client running on my local computer and decided to investigate the logs.
More strangely, while some of incoming connection attempts end up with network error, some others connect successfully "Handshake success". No pattern could be spotted between successful and failing ones.
Collected a pcap of both sides (my local machine and server) but could not spot anything unusual. After the Handshake, which is received without issues, server sends a FIN packet in order to close the connection.
Changing the network connection (used tethered 4G) made it to work - but again, connection between the two machines is solid.
Any guidance on how to proceed? Any way of increasing logging for handshake_manager beyond just a "network error"?
Thanks!
The text was updated successfully, but these errors were encountered: