- cross-posted to:
- opensource@lemmy.ml
- privacy@lemmy.ml
- cross-posted to:
- opensource@lemmy.ml
- privacy@lemmy.ml
Proton’s mission, funding sources, independence, and community are some of the reasons we’re more resilient than other privacy-first companies.
The Linux client isn’t perfect, but you can download the openVPN config file and set up individual server connections yourself. It’s all laid out on their website, fairly simple. If you know what you’re doing, you can also edit the config files to allow IP-based split tunneling.
Ah, well the VPN client I config in my router so as long as Proton uses OpenVPN or WireGuard I should be able to get it to work, even though I barely know what I’m doing. Converting settings files manually to settings in pfSense is doable.
I can’t speak about pfsense or router-based configs, I have zero experience there. The Proton website does have openVPN and wire guard manual setup instructions though. You could try it with a free account first to make sure everything works before committing to paying for it. If you’re interested, I can show you the changes I made to the openVPN config file to allow split tunneling. Again though, I don’t know how that translates to pfsense.
I tried their OpenVPN config files but I always get IP leaks. Any idea on how to fix that? :(
I believe there’s a way to do it using iptables, but I’d have to look into it more again. You might get more experienced people answering if you search for “openVPN force traffic through VPN iptables” or something similar. Let me know if that helps!
Turns out the problem is that Proton does not support IPV6, at least via OpenVPN or WireGuard. Disabling ipv6 fixes the problem, though I don’t really enjoy that solution :|
Ahh yeah, that sounds right. When you use the official GUI on Linux it creates an IPV6 killswitch connection along with the VPN connection. Sorry, I don’t have any better answers for ya there.