AirVPN’s Eddie client doesn’t have dedicated “split-tunneling,” but it does have a feature that allows for the same thing, as long you only need your torrent client and/or Firefox to go through the VPN.
In Eddie, first go to Settings → Network Lock, and chose “None” for “Mode.”
Then, go to Settings → Routes. This allows you to specify if a destination IP should be excluded or included by Eddie. What is needed is to specify that all IP addresses should be excluded. The way to do this is via CIDR ranges, which will allow us to refer to all possible IP addresses. You have to enter the CIDR ranges for all IP addresses from 1.1.1.1 to 255.255.255.255. For some reason, starting at 0.0.0.0 doesn’t work.
What this looks like is adding a Route (via the green plus button), selecting “Outside the VPN tunnel” for “When connected,” and under “IP / Host / Range,” entering a CIDR block. You’ll need to do this manually for each CIDR block:
1.1.1.1/32
1.1.1.2/31
1.1.1.4/30
1.1.1.8/29
1.1.1.16/28
1.1.1.32/27
1.1.1.64/26
1.1.1.128/25
1.1.2.0/23
1.1.4.0/22
1.1.8.0/21
1.1.16.0/20
1.1.32.0/19
1.1.64.0/18
1.1.128.0/17
1.2.0.0/15
1.4.0.0/14
1.8.0.0/13
1.16.0.0/12
1.32.0.0/11
1.64.0.0/10
1.128.0.0/9
2.0.0.0/7
4.0.0.0/6
8.0.0.0/5
16.0.0.0/4
32.0.0.0/3
64.0.0.0/2
128.0.0.0/1
If someone knows of a way to automate this, I would love to hear. That said, doing it manually only took me a couple minutes.
So now all IP addresses are set to go outside of the VPN tunnel. All that needs to happen now is to bind your torrent client to Eddie. In qBittorrent, this just looks like going to Tools → Options → Advanced → Network Interface, and selecting Eddie. Now the torrent client goes through AirVPN, while everything else bypasses it. As seen in this test from ipleak.net, ipleak registers my real IP via the browser (and doesn’t detect the AirVPN exit node), yet the torrent address detection registers only the Eddie VPN. [EDIT: upon further checking, I realized that ipleak might detect the VPN address for the browser as well and the exit node, but it will still also detect your real IP. Seeing the exit node and the VPN IP doesn’t mean it’s not working. whatismyipaddress.com still shows my real IP with the VPN on].
I haven’t tested this, but if you want a Firefox instance to go through the VPN, I believe you can do this via ForceBindIP: GitHub - ixjb94/ForceBindIP-Gui: A GUI For ForceBindIP if you follow the ReadMe and choose the “Eddie” option as your Internet Connection.
I have only tested this on Windows 10, but I imagine it works for others.
