Skip to content

Route torrents through SOCKS5 proxies - #75

Merged
Linuxuser67 merged 2 commits into
mainfrom
torrent-via-proxy
Sep 18, 2026
Merged

Linuxuser67 merged 2 commits into
mainfrom
torrent-via-proxy

Conversation

@Linuxuser67

Copy link
Copy Markdown
Owner

Torrents no longer unconditionally bypass the proxy.

  • ResolvedProxy::torrent_socks_url: SOCKS5 only (socks5h normalizes to socks5); HTTP(S) proxies stay direct.
  • plan_torrent_net (pure, tested): under SOCKS, DHT off, listen port 0, UDP trackers dropped — the engine cannot proxy any of those, so they go dark instead of leaking. Invalid manual proxy fails the row loudly like every other engine.
  • Session connect.proxy_url set at creation (same creation-scoped rule as DHT/listener: edits apply to new sessions).
  • Subtitle + pot: "Torrents follow SOCKS5 proxies only".

CONFLICT NOTE: #74 touches the same subtitle line — merge in order (#74 first) or close #74 in favor of this.

239 passing (5 new), clippy/fmt clean. No live-torrent test possible (no seed harness); peer path verified against librqbit 9.0.1 sources (validate() on both add paths, no local DNS on peer path, reqwest-proxied HTTP trackers).

@Linuxuser67
Linuxuser67 merged commit 48ee71c into main Sep 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant