Linux 101 stuff. Questions are encouraged, noobs are welcome! @lemmy.world Hellmo_luciferrari @lemm.ee 1w ago

UFW and a Windows KVM with Virt-Manager

So, I finally ditched Windows... All except for my need for a VM to use some hardware that aren't supported in Windows.

I setup a Virtual Machine with Virt-Manager for a Windows VM but the network traffic is being blocked by UFW. If I disable UFW the Windows VM can pull an IP, which is static as is, and even after turning UFW back on, the network traffic is still allowed.

I am in need of some help with networking for the VM.

<interface type="network">
  <mac address="52:54:00:d7:8f:48"/>
  <source network="default" portid="d7ff3b1f-2c9b-4a62-b9e0-180855f14de7" bridge="virbr0"/>
  <target dev="vnet2"/>
  <model type="e1000e"/>
  <link state="up"/>
  <alias name="net0"/>
  <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
</interface>

This is the networking setup within Virt-Manager.

Any advice for getting network access on the VM?

6 comments

Are you allowing dhcp (:53 tvp/udp) through the FW? If not try
sudo ufw allow bootps
sudo ufw allow 53/udp
sudo ufw allow 53/tcp

or maybe give it a static IP on the defined virt-manager network and allow traffic from that IP
sudo ufw allow from 192.168.150.xxx or whatever the dhcp network is
- Thank you for the suggestion. I will for sure give this a shot later tonight when I am able to access my home desktop.
  
  No prob, let us know how it goes. Also, thinking more about it, you may want to go the static IP route for 2 reasons
  
  You wont be introducing a 2nd dhcp server to your home/production network
  
  You'll always know the IP of the guest VM(s)
  
  w/ regards to the first issue I guess you could just allow :53 and bootps from the dhcp subnet that virt manager created. Something like
  sudo ufw allow from 192.168.122.0/24 to any port 53 where 192.168.122.0/24 is the subnet virt-manager created for dhcp
  
  I think that'll allow both tcp and udp. I haven't used ufw in a while, my RHEL based distros switched to firewalld, but the concepts are the same, just different syntax. I do believe you'll need udp open as IIRC during DORA the initial DISCOVER is sent over udp, and somewhere between OFFER and REQUEST it switches to tcp...but I also haven't had to troubleshoot dhcp in a while, and I have forgotten a lot. Either way let us know how it goes!

6 comments