Qubes
Sending packets over Qubes tubes
Get Qubes working the way you want, find out how networking works, and start making your own qubes.
This screenshot cannot convey how choppy video streaming is in Qubes.
Despite each qube’s application menu only having a few entries, there are quite a few utilities installed by default. If you want to give them a menu shortcut, go to that qube’s settings (in Qube Manager) and go to the Applications tab. Most likely you’ll want to give KeePassXC an icon in the Vault qube. Any GUI apps you later install find their way into that Applications tab. You can use the refresh menu button to update the main menu immediately.
Secure networks
Each qube has its own private IP (beginning with 10; you can see them in Qube Manager) and the AppVMs can’t see or even ping each other (try it). You’ll also see in Qube Manager that Dom0 has n/a in its IP address column, as it has no network access. We mentioned the sys-firewall (used by everything except Whonix) and sys-whonix NetVMs previously. And now if you dig deeper, you can see that the sys-whonix qube actually uses sys-firewall under the hood. This makes sense as we want Tor traffic to be subject to firewall rules, too. Going one step deeper, you can see that the firewall qube uses sys-net, which is the qube that actually connects to any Wi-Fi or Ethernet adaptors.