A fully VPN’ed family member got hit with an automated copyright strike and when looking into how it happened I found out that using the default qBittorrent config with a killswitch-enabled ProtonVPN meant that the home IP address was being leaked. I verified it through a few tools, including ipleak(dot)net’s fake magnet link feature which showed both the VPN and home IPs when connected. I’m at best a tinkerer so I’m not sure if this is a Proton-exclusive problem at all, or if the killswitch useage is even relevant, but that’s what they were using and figured this all might be worth mentioning since it was certainly a shock to us and not something we’ve seen brought up before.
The solution was to change which network interface qBittorrent was set to use via “Tools > Preferences > Advanced > Network interface”. Which one to pick will depend on the protocol you’re using in Proton’s client, but unless you’re confident in what you’re doing I’d recommend testing each with the ipleak(dot)net (or similar) torrent tool until you’re only seeing the VPN IP show up.
Hope this is useful! (and not common knowledge that we were just wildly ignorant of)
Sounds like they were using a vpn on their device but didn’t actually bind it to qbit. The solution you posted is exactly how you bind it to the vpn. So now even if the vpn leaks, qbit will cease to up/dwn. Glad you guys learned and hopefully you guys never get a letter again.
deleted by creator
It’s an ad
deleted by creator
The point is that the killswitch doesn’t seem to do much, at least on Linux in my experience. I’ve never had it work.
Transmission does this by explicit binding to the IP for a singular interface, which seems safer to me. By only sending data on the IP for the VPN, if anything goes wrong it will just literally refuse to send packets on the non-VPN network.
You can do this in qbt as well, op just didn’t have it set