Network interface bind not respected for tracker announces #5086

New issue

Closed

opened 2026-02-21 17:39:37 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 17:39:37 -05:00

Owner

Originally created by @Tadsz on GitHub (Jan 3, 2017).

qBittorrent: 3.3.7
Qt: 5.7.0
libtorrent: 1.0.10.0
boost: 1.61.0
OS version: W10 Pro

I did not see a fix for this problem in the changelog for upcoming versions

When bound to a specific network interface (VPN), some trackers are still announced over the default network interface causing another IP to bleed to the tracker. Not all trackers continue to work but a lot keep working (did not find a difference for http/https)

Steps to reproduce:

Bind qBittorrent to a disconnected interface (VPN, but disconnected) and restart qBittorrent for changes to take effect. This should mean no network traffic to trackers and therefore announces must fail.
Add a list of torrents with various trackers as it's only a fraction of trackers that announce outside of the bound interface.
Check which trackers report a working announcement and check with those trackers to see what IP is reported.

When a firewall rule is made to block qBittorrent and that rule applied only to the not-bound interface while the bound interface (VPN) is disconnected, then all trackers fail. If the bound interface is connected then all trackers succeed. The firewall log still shows a lot of connections through the not-bound interface.

Originally created by @Tadsz on GitHub (Jan 3, 2017). qBittorrent: 3.3.7 Qt: 5.7.0 libtorrent: 1.0.10.0 boost: 1.61.0 OS version: W10 Pro *I did not see a fix for this problem in the changelog for upcoming versions* When bound to a specific network interface (VPN), some trackers are still announced over the default network interface causing another IP to bleed to the tracker. Not all trackers continue to work but a lot keep working (did not find a difference for http/https) ### Steps to reproduce: - Bind qBittorrent to a disconnected interface (VPN, but disconnected) and restart qBittorrent for changes to take effect. This should mean no network traffic to trackers and therefore announces must fail. - Add a list of torrents with various trackers as it's only a fraction of trackers that announce outside of the bound interface. - Check which trackers report a working announcement and check with those trackers to see what IP is reported. When a firewall rule is made to block qBittorrent and that rule applied only to the not-bound interface while the bound interface (VPN) is disconnected, then all trackers fail. If the bound interface is connected then all trackers succeed. The firewall log still shows a lot of connections through the not-bound interface.

deekerman

2026-02-21 17:39:37 -05:00

closed this issue
added the
Network

Security
labels

deekerman commented

2026-02-21 17:39:42 -05:00

Author

Owner

@ghost commented on GitHub (Jan 26, 2017):

I can confirm also.

Looking at Wireshark, qBittorrent also attempts to retrieve the favicons for the trackers with a HTTP GET request outside of the VPN interface, which stores a cookie each time. I also noticed the search engine is excluded from using the specified interface, which has already been reported here #3116.

@ghost commented on GitHub (Jan 26, 2017): I can confirm also. Looking at Wireshark, qBittorrent also attempts to retrieve the favicons for the trackers with a HTTP GET request outside of the VPN interface, which stores a cookie each time. I also noticed the search engine is excluded from using the specified interface, which has already been reported here #3116.

deekerman commented

2026-02-21 17:39:42 -05:00

Author

Owner

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

Maybe qualifies as another example of this?:
qBt traffic escapes allowed interface https://github.com/qbittorrent/qBittorrent/issues/5272

@Seeker2 commented on GitHub (Jul 14, 2017): Maybe qualifies as another example of this?: qBt traffic escapes allowed interface https://github.com/qbittorrent/qBittorrent/issues/5272

deekerman commented

2026-02-21 17:39:42 -05:00

Author

Owner

@ngosang commented on GitHub (Sep 16, 2018):

We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.

@ngosang commented on GitHub (Sep 16, 2018): We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0). Please, update to last release and, if the bug/error/crash is still present, open another issue. Thank you.

deekerman referenced this issue

2026-02-21 20:41:33 -05:00

[Tool] Batch close old issues #10312

deekerman referenced this issue

2026-02-21 20:41:34 -05:00

[Tool] Batch close old issues #10312