How would i set up Qubes so that a VPN is always on, with a killswitch in the whole of Qubes 4.1?
Right now i have created a standalone VPN appVM as the qubes documentation says, with iptables.
" Set up a ProxyVM as a VPN gateway using iptables and CLI scripts"
Then i switched the personal or untrusted to use a VPN in Qubes settings net cube.
But now i’m wondering if instead of setting cubes to use the VPN, is it not better to set all of qubes to connect through a VPN? And if i then use any Appvm, cubes, they will all connect through the VPN, and also TOR. So it’s tor-over-vpn.
The first connection is made to a vpn, and the second is tor through that VPN.
How do i set that up in Qubes 4.1? Could i just set the sys-net to use the sys-VPN and then all of qubes traffic goes through a vpn ?
Ok, is that the optimal way if you want all of the traffic to go through a VPN in Qubes 4.1?
Are there any documentation for this? I read in those that you can set up which cubes you want to use…
But if i use my way whonix would use tor-over-vpn instead of tor-internet as now…
And that would give more security as-well.
What do you mean? No. And that’s irrelevant to my question…
I’m not asking about the clock…
I’m asking about how qubes work, and if i can get all of the traffic out from Qubes through a VPN that is always on, and that has a killswitch if it goes down.
I’m also wondering in what ways qubes is “leaking” the real IP as default? Everything apart from the whonix is “leaking” the real ip i’m guessing.
If i want a VPN as a filter, how do i set that up is my question. If anyone has managed that i would appreciate if you could help me with an answer.
Yes that’s irrelevant, and i don’t care about the clock…
I mean leaking outside of the Qubes OS… past my router. Hiding the real ip as in putting a lock on a house.
Answer if you have experience with this. Or anyone else. You are offtopic. Thanks
Same… I confuse them. I mean. I want a VPN as the first connection to the internet, and then after that a tor connection that goes inside of that VPN. The ISP can see a vpn, whonix would run inside. To my understanding that gives a little bit of “anonymity”, or security online.
That doesn’t make sense. sys-net is essentially your device controller for the hardware that allows you to connect to the internet. Either your wifi card or ethernet controller. There is no VPN service without something to plug into. One of the reasons sys-firewall is there is to prevent DMA attacks on your front end VMs (due to sys-net being directly connected to your hardware controller). So those two VMs are the bare essentials for secure connectivity. Then you add a VPN qube with your firewall IP tables configured and a kill switch, etc.
Also, don’t run any apps in sys-net and don’t connect any appVMs to directly to sys-net. sys-net and sys-firewall should be utilized as a pair and everything else should be in front of them.