bind to interface still exposes searches #2567

New issue

Open

opened 2026-02-21 16:17:28 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-21 16:17:28 -05:00

Owner

Originally created by @aleqx on GitHub (May 28, 2015).

I like the bind to interface feature but the searches are still sent through the main NIC, regardless of which NIC qBT is bound to (I did restart).

I'm using Windows 8.1 Pro x64. Used Wireshark to reveal this.

I noticed searches are done by launching a separate Python process, which doesn't look bound to the IP from the preferences. Python can be bound to an interface and I would expect qBT to do that if the option is set in the settings.

I noticed each search engine uses a python script. You can just embed that into a Python wrapper that first binds Python to a specific network interface.

I understand it's extra work but right now the "bind to interface" feature exposes private activity. If a user activates "bind to interface" then they know what they are doing and expect all the comms to go through that NIC, including searches, i would say.

Originally created by @aleqx on GitHub (May 28, 2015). I like the bind to interface feature but the searches are still sent through the main NIC, regardless of which NIC qBT is bound to (I did restart). I'm using Windows 8.1 Pro x64. Used Wireshark to reveal this. I noticed searches are done by launching a separate Python process, which doesn't look bound to the IP from the preferences. Python can be bound to an interface and I would expect qBT to do that if the option is set in the settings. I noticed each search engine uses a python script. You can just embed that into a Python wrapper that first binds Python to a specific network interface. I understand it's extra work but right now the "bind to interface" feature exposes private activity. If a user activates "bind to interface" then they know what they are doing and expect all the comms to go through that NIC, including searches, i would say.