starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

IP leak to tracker during announce #5773

New issue

Closed

opened 2026-02-21 18:02:19 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-21 18:02:19 -05:00

Owner

Originally created by @pnjun on GitHub (Jul 11, 2017).

qBittorrent version and Operating System:

v3.3.13 64bit
OSX 10.11.5

What is the problem:

I have a VPN service on the interface tun0. I configured qbittorrent to bind to that interface. When the VPN is on, the announce to trackers is done through that interface, and the tracker sees my VPN IP. If the VPN goes down, the P2P traffic stops, but qbittorrent announces my real IPV6 to the tracker. If i turn the VPN on again, P2P traffic resumes and announce goes back to the VPN IP.

What is the expected behavior:

Use only tun0 interface for announce. Don't perform any announce if tun0 is down.

Steps to reproduce:

Bind to tun0
Start VPN
Check announce IP on ipleak.net
Download for a while
Stop VPN
Check ipleak again, real IP is leaking.

Extra info(if any):

Originally created by @pnjun on GitHub (Jul 11, 2017). ### qBittorrent version and Operating System: v3.3.13 64bit OSX 10.11.5 ### What is the problem: I have a VPN service on the interface tun0. I configured qbittorrent to bind to that interface. When the VPN is on, the announce to trackers is done through that interface, and the tracker sees my VPN IP. If the VPN goes down, the P2P traffic stops, but qbittorrent announces my real IPV6 to the tracker. If i turn the VPN on again, P2P traffic resumes and announce goes back to the VPN IP. ### What is the expected behavior: Use only tun0 interface for announce. Don't perform any announce if tun0 is down. ### Steps to reproduce: Bind to tun0 Start VPN Check announce IP on ipleak.net Download for a while Stop VPN Check ipleak again, real IP is leaking. ### Extra info(if any):

deekerman

2026-02-21 18:02:19 -05:00

closed this issue
added the
Duplicate
label

deekerman commented

2026-02-21 18:02:26 -05:00

Author

Owner

@Seeker2 commented on GitHub (Jul 12, 2017):

This seems similar to:
https://github.com/qbittorrent/qBittorrent/issues/5272 qBt traffic escapes allowed interface
https://github.com/qbittorrent/qBittorrent/issues/6668 If network interface connection drops while using proxy torrent still downloads

@Seeker2 commented on GitHub (Jul 12, 2017): This seems similar to: https://github.com/qbittorrent/qBittorrent/issues/5272 qBt traffic escapes allowed interface https://github.com/qbittorrent/qBittorrent/issues/6668 If network interface connection drops while using proxy torrent still downloads

deekerman commented

2026-02-21 18:02:26 -05:00

Author

Owner

@zeule commented on GitHub (Jul 12, 2017):

Closing as duplicate of #5272. Thanks, @thalieht.

@zeule commented on GitHub (Jul 12, 2017): Closing as duplicate of #5272. Thanks, @thalieht.

deekerman commented

2026-02-21 18:02:26 -05:00

Author

Owner

@pnjun commented on GitHub (Jul 12, 2017):

Sorry, but it's not the same issue. Those issues refer to qb downloading torrents after the vpn goes down, which is not my case. As i said, when the VPN goes down, torrent traffic rightly stops.

The problem is that qb keeps announcing to the trackers using the other (en1) interface.

@pnjun commented on GitHub (Jul 12, 2017): Sorry, but it's not the same issue. Those issues refer to qb downloading torrents after the vpn goes down, which is not my case. As i said, when the VPN goes down, torrent traffic rightly stops. The problem is that qb keeps announcing to the trackers using the other (en1) interface.

deekerman commented

2026-02-21 18:02:26 -05:00

Author

Owner

@Seeker2 commented on GitHub (Jul 12, 2017):

Your problem is it's "half-fixed" (not continuing to download when the VPN goes down), but it's still a problem because the trackers are still being updated by qBT.
That's why I said your problem was similar to #5272 but not identical to it. They probably share the same underlying cause -- buggy tracker update logic, doing updates when it SHOULDN'T.

In my barely-related case, tracker updates to ALL trackers were even done while the torrent was paused: https://github.com/qbittorrent/qBittorrent/issues/6137
...admittedly the extra criteria was I was doing a force recheck on the torrent, but that shouldn't be triggering tracker updates either!

@Seeker2 commented on GitHub (Jul 12, 2017): Your problem is it's "half-fixed" (not continuing to download when the VPN goes down), but it's still a problem because the trackers are still being updated by qBT. That's why I said your problem was similar to #5272 but not identical to it. They probably share the same underlying cause -- buggy tracker update logic, doing updates when it SHOULDN'T. In my barely-related case, tracker updates to ALL trackers were even done while the torrent was paused: https://github.com/qbittorrent/qBittorrent/issues/6137 ...admittedly the extra criteria was I was doing a force recheck on the torrent, but that shouldn't be triggering tracker updates either!

deekerman commented

2026-02-21 18:02:26 -05:00

Author

Owner

@zeule commented on GitHub (Jul 12, 2017):

@pnjun, feel free to reopen, but my logic is that fixing #5272 has to fix this issue too.

@zeule commented on GitHub (Jul 12, 2017): @pnjun, feel free to reopen, but my logic is that fixing #5272 has to fix this issue too.

deekerman commented

2026-02-21 18:02:27 -05:00

Author

Owner

@pnjun commented on GitHub (Jul 14, 2017):