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
My usecase is similar to #4904 : I setup proxy to connect to trackers while using direct connections with peers. In this configuration after #4904 is solved, UDP traffic is fine; however, any incoming TCP connection is accepted but immediately closed by the library.
It seems that the fix in #4909 leaves out a check in session_impl::on_accept_connection:
More generally, I'm not sure whether the check in on_accept_connection makes sense at all: if we don't want to deal with the connection, we shouldn't be even listening on the port. Removing the check seems to fix the problem for me.
libtorrent version (or branch): 1.2.12.0, built in qBittorrent v4.3.3
platform/architecture: Windows 10 Build 19042.804, 64-bit
The text was updated successfully, but these errors were encountered:
My usecase is similar to #4904 : I setup proxy to connect to trackers while using direct connections with peers. In this configuration after #4904 is solved, UDP traffic is fine; however, any incoming TCP connection is accepted but immediately closed by the library.
It seems that the fix in #4909 leaves out a check in
session_impl::on_accept_connection
:libtorrent/src/session_impl.cpp
Line 2698 in 985fc00
At the very least, I think it should be synchronized with
session_impl::reopen_listen_sockets
libtorrent/src/session_impl.cpp
Lines 1952 to 1953 in 985fc00
More generally, I'm not sure whether the check in
on_accept_connection
makes sense at all: if we don't want to deal with the connection, we shouldn't be even listening on the port. Removing the check seems to fix the problem for me.libtorrent version (or branch): 1.2.12.0, built in qBittorrent v4.3.3
platform/architecture: Windows 10 Build 19042.804, 64-bit
The text was updated successfully, but these errors were encountered: