By “this setup” you mean the VM itself? I am having several projects that I don’t want to be linked to each other. By websites, potential spies as well by authorities. Therefore I want to maximize my security and privacy and also have different identities that I want to achieve with the VMs.
If you meant something else, I don’t know what you mean exactly. Right now, I cannot access WiFi on my VM since it only offers wired connection and the WiFi settings say I need a WiFi adapter. That’s where I am now and I am unsure of what to do. I got the guide from Vladislav but a second opinion is always appreciated.
I have had a problem with the guide though because I don’t know how to modify the kernel command line (I have asked another question for this, it’s my newest one).
Well, exposing you wifi adapter directly into those environments will reduce your anonymity, not increase it. It seems like your proposed solution is not only much more complicated to implement but contrary to your goals.
Just use the virtual lan adapter in the VM. You can control which network it is connected to on the host.
First, go to connection details and look at this screen:
If you have more than network adapter on the host you will have multiple items on the left where I only have “default”
Yes, both windows look exactly as mine. It still can’t connect and shows no wired connections.
I noticed that when I boot the VM, it says “Failed to start network manager wait online”.
Perhaps it has something to do with this.
The settings are the same though.
When I installed my VM I selected bridge instead of nat and selected the virbr0 interface on the host.
On the VM I get this, which you see is different than yours in that it does not show the upper line that says NAT. Also you see the output of “ip a” as well. For me it just works.
Since each VM gets its own IP and the host does the NAT automatically it has as good a security as it gets. In fact doing it this way I have double NAT. First in the host, then in the gateway router.
BTW, when I posted that pic I noticed that I had neglected to update the VM name when I did the upgrade from 33 to 34. It is actually running fedora 34 on a fedora 34 host.
I have adjusted the NIC settings just like that (set to bridge, type in virbr0 for the device) but it still doesn’t work.
I also don’t get an IP address like you did. It still says “Unknown”.
