Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)BN
Boris_NotTooBadinoff @lemmy.world
Posts 1
Comments 567
UFW and a Windows KVM with Virt-Manager
  • 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

    1. You wont be introducing a 2nd dhcp server to your home/production network
    2. 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!

  • UFW and a Windows KVM with Virt-Manager
  • 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

  • iiiiiiitttttttttttt @lemmy.world Boris_NotTooBadinoff @lemmy.world

    Working support, some days it rings true

    I think we've all been there 😂

    1