Join GitHub today
[PROBLEM] qbt can expose DSL-IP, although VPN is used #9658
Please provide the following information
qBittorrent version and Operating System
v4.1.3, Windows 32bit (not relevant)
What is the problem
For some reason, qbt detects my DSL-IP (xx.xxx.14.36) in the short time-period while e.g. router/gateway/modem boots up and the VPN has not been established and the killswitch of the firewall is not yet active.
(The DSL-IP sometimes is visible in peer-list of a torrent; I also have seen that the DSL-IP and VPN-IP both are in the peer-list at the same time! Showing any own IP in the peer-list is also a bug; not serious, but it exposes the problem and pointed me to it.)
What is the expected behavior
Don't expose the DSL-IP. I do not know how this could be done,
Steps to reproduce
Might be difficult.
Extra info (if any)
The VPN-provider can't publish my DSL-IP. Also I am quite sure that the killswitch of the firewall in my router works in general.
@FliessendWasser: Yes. It always was. I know there are concerns regarding security, but from a different perspective. Ports are closed and UPnP is disabled on my DSL router, also canyouseeme reports that port is closed.
There is nothing QB can do if it is active prior the VPN with related kill switch are in play, not sure how it is expected otherwise. Just make sure that QB starts only after VPN with related kill switch are in play.
Rather fail-safe is the socks5 proxy feature anyway, lots of VPN provide such gateways, plus the https://github.com/qbittorrent/qBittorrent/wiki/Anonymous-Mode
This is not really a code issue or sort of bug and perhaps better perused in the qbit forum
I use Comodo(there might be other firewalls but i haven't seen any that do the same) to block my p2p clients from using my standard internet connection by blocking all them from all communication except by a network zone for my vpn that i create with ip addresses used by the vpn provider. Then your p2p client can't communicate with anything except your vpn.