Skip to content
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

"Use proxy for peer connections" doesn't proxify peer connections #11211

Open
emanruse opened this issue Sep 9, 2019 · 7 comments

Comments

@emanruse
Copy link

commented Sep 9, 2019

qBittorrent version and Operating System

4.1.7, openSUSE Leap 15

If on linux, libtorrent-rasterbar and Qt version

1.1.13.0
5.9.4

What is the problem

"Use proxy for peer connections" doesn't proxify peer connections.

What is the expected behavior

It should do what it says.

Steps to reproduce

  1. Set up and start a local tor service
  2. In QBT set Proxy Server Type=SOCKS5, Host=127.0.0.1, Port=9050
  3. Activate also "Use proxy for peer connections"
  4. Monitor connections using:
watch 'ss -tuapn | grep -i qbittorrent | grep -vi 127.0.0.1'

Result:

Actual direct (not proxified) connections to peers are visible, matching the same IP addresses of the seeders and leechers which can be seen in QBT.

Extra info(if any)

Connections to tracker work (through Tor).

"Disable connections not supported by proxies" stops any and all connections (0 B/s). I don't know if this is normal and how to set it correctly in order to fully torify everything. If possible please explain.

@Chocobo1

This comment has been minimized.

Copy link
Member

commented Sep 9, 2019

https://legaltorrents.com/tor/#Tor_for_torrenting_4_downsides_you_must_know_about
https://blog.torproject.org/bittorrent-over-tor-isnt-good-idea
https://www.reddit.com/r/TOR/comments/2u3j6m/why_exactly_is_torrenting_over_tor_bad_and_how/
Probably a bad idea to torrent over Tor.

Actual direct (not proxified) connections to peers are visible, matching the same IP addresses of the seeders and leechers which can be seen in QBT.

"Disable connections not supported by proxies" stops any and all connections (0 B/s).

Are those connections over UDP? If yes then it is expected and explained in the above links.

@emanruse

This comment has been minimized.

Copy link
Author

commented Sep 9, 2019

@Seeker2

This comment has been minimized.

Copy link

commented Sep 10, 2019

Could be related to this probably libtorrent related bug:

http://dev.deluge-torrent.org/ticket/2149 deluge ignoring proxy settings
"I just monitored Deluge with Wireshark and found that Deluge is connecting directly to peers despite having a working proxy. However I have noticed some interesting behavior:
If I change one number in the proxy IP, for example, to a non-working proxy, no downloads work; everything is frozen. So Deluge will only download given a working proxy; it's just not using that proxy."

@emanruse

This comment has been minimized.

Copy link
Author

commented Sep 10, 2019

@Seeker2

This comment has been minimized.

Copy link

commented Sep 10, 2019

You misunderstood the point there -- the poster used that example to demonstrate that Deluge was recognizing the proxy and connecting to it...but Deluge wasn't using the proxy for peer/seed connections!

@Chocobo1

This comment has been minimized.

Copy link
Member

commented Sep 11, 2019

@emanruse
Seems you have the same symptom as #7734 and there are some discussion going on there currently.

@Chocobo1 Chocobo1 added Network Proxy and removed Network labels Sep 11, 2019

@emanruse

This comment has been minimized.

Copy link
Author

commented Sep 11, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.