KarlinQubes,
This is definitely easy mode. Thank you!
I am trying to learn as I go (lots of rabbit holes). Someone’s script doing it all for me is nice and easy. I’m also interested in the nuts and bolts of it so I can write my own scripts or tweak other people’s scripts.
I see hkbakke has a custom config file for the WireGuard network config. Which subnet/dns should be in there? Does it need to match my net-vpn (based on TemplateVM fedora-34-wireguard) IP/DNS? :EDIT: This is provided by my VPN provider. Sorry for the dumb Q.
I never had confusion on the purpose and usage. That is a good analogy though.
Windows does shit stupid. I’d rather fumble in Linux terminology.
Just to ensure I’m understanding the workflow here:
1.) Clone base template (fedora in this case) called fedora-34-wireguard, install WireGuard, shutdown
2.) Create new Qube
Name and label: net-vpn-narnia
Type: AppVM
Template: fedora-34-wireguard
Networking: default (sys-firewall)
Advanced Tab: Enable ‘Provides network access to other qubes’
3.) Repeat #3 named ‘net-vpn-missing_sock_universe’
4.) Configure Wireguard unique tunnels on each net-vpn-* AppVM, shutdown/restart
5.) Create AppVM named ‘fedora-34-vpn-narnia’ using networking ‘net-vpn-narnia’
6.) Create AppVM named ‘fedora-34-vpn-missing_sock_universe’ using ‘net-vpn-missing_sock_universe’
7.) … so let’s just rest.
Does this still hold true? If I did my 7 steps correctly?
Thanks for this rabbit hole.