Leaderboard

In the scripts I provide in the wiki the VPN routing table entries are suppressed entirely. But those call and configure the openvpn or wireguard client program directly. They don't use Eddie. If someone wants to use Eddie without trying to control the openvpn or wireguard client inside it (i.e. just the way it comes), then the VPN will attempt to install its gateway as the default. You could just remove them afterwards. But a user may want to put them back again later in order to use the VPN with their browser. So you would need a script to remove and another to reinstall the VPN gateway. Also, I prefer not to let the VPN be the default gateway even for a brief moment. If I hide the VPN gateway before I start the VPN, then it will never be the default. And this is how the Windows scripts I provided work. So it should be familiar to tranquivox69.

Of course those came originally from the wiki I wrote on github. I guess the scripts I posted there for Linux are not appealing because they do not use Eddie. I don't use Eddie. So I would not want to invest a huge effort coming up with scripts to accommodate Eddie. Particularly since AirVPN is about to release a version of Eddie that will address this. But you could have a script that overrides the VPN gateway in exactly the same way that Windows script does, By adding routing table entries that will hide the routing table entries the VPN will install. You could run it before you start Eddie. Or have Eddie start it as you do in Windows. It would need to determine what the original gateway IP address was. Or you might be able to just hard-code that. Does it change when you reboot? Depends on your router settings. The problem is that on Linux, unlike Windows, this does not set up source address routing for you. You would need another script to use the ip command after the VPN has come up to do that. There is an example in my wiki page about Linux. That script would have to determine the VPN IP addresses to use. For Wireguard the addresses shouldn't change when you switch servers. So you could just hard-code them. In fact, for Wireguard, if you hard-code them you might be able to do that in the same script that hides the VPN gateway. I think Eddie may let you run that second script automatically, after the VPN is up. Then you could bind qbittorrent to the VPN interface for OpenVPN or to the VPN address for Wireguard. Hope that helps. My approach is to offer information on how to "do it yourself" to folks who are willing to learn. Because I do not want to promise to maintain some software package. Even the scripts I put in the wiki are just meant as examples.

Containerizing things is no doubt more secure. But requires much more work and technical skill. Many rely on containers that are written with great enthusiasm, and then very quickly abandoned by the author. Maybe after they graduate? I see posts in forums all the time about how the containerized version of qbittorrent they have been using isn't being updated. Or they want know how they can browse through the VPN too. Or run some other app through the VPN. Not just qBittorrent. And this brings me back to wondering what approach AirVPN will take inside Eddie.