Arch Linux

proledatarian

Member

Registered: 2022-02-11

Posts: 20

[SOLVED] ufw is blocking network of virtual maschine?

I'm using virt-manager to test different installations of Arch Linux and/or Arch Linux ISOs. I'm using ufw and have set it to allow from my home network (192.168.0.0/24 and 192.168.0.0/16). My virtual machines do not have access to the network or internet. I even allowed the VMs IP range specifically (192.168.122.0/24), but it's still not working and I don't know why? When I disable ufw everything works fine.

Last edited by proledatarian (2024-08-23 13:39:37)

---

Gitea | AUR-Packages

jnnj

Member

Registered: 2024-08-22

Posts: 5

Re: [SOLVED] ufw is blocking network of virtual maschine?

Hi proledatarian,
please provide us relevant part (better is: whole output) of sudo ufw status numbered. Maybe very silly question: did You enable DNS/HTTP/HTTPS ports? This ufw command do on your bare metal computer.

What is output of traceroute 95.217.163.246 (ip addr of archlinux.org -> must be "404 nginx")? (do on virtualized PC's)

proledatarian

Member

Registered: 2022-02-11

Posts: 20

Re: [SOLVED] ufw is blocking network of virtual maschine?

I reset ufw. Here are my current rules:

Status: active

     To                         Action      From
     --                         ------      ----
[ 1] Anywhere                   ALLOW IN    192.168.0.0               
[ 2] 22                         LIMIT IN    Anywhere                  
[ 3] 1714:1764/udp              ALLOW IN    Anywhere                  
[ 4] 1714:1764/tcp              ALLOW IN    Anywhere                  
[ 5] 22 (v6)                    LIMIT IN    Anywhere (v6)             
[ 6] 1714:1764/udp (v6)         ALLOW IN    Anywhere (v6)             
[ 7] 1714:1764/tcp (v6)         ALLOW IN    Anywhere (v6)      

And here's the output of traceroute from my VM, with ufw disabled:

traceroute to 95.217.163.246 (95.217.163.246), 30 hops max, 60 byte packets
 1  _gateway (192.168.100.1)  0.239 ms  0.149 ms  0.093 ms
 2  fritz.box (192.168.178.1)  0.448 ms  0.529 ms  0.788 ms
 3  192.0.0.1 (192.0.0.1)  12.280 ms  13.296 ms  14.133 ms
 4  eft1001aihd001.versatel.de (62.214.42.186)  15.708 ms  16.601 ms  17.504 ms
 5  xnl1002aihb001.versatel.de (80.249.209.109)  36.399 ms  37.255 ms  38.153 ms
 6  amsix-gw.hetzner.com (80.249.209.55)  39.003 ms  30.923 ms  31.439 ms
 7  * * *
 8  core52.sto.hetzner.com (213.239.252.82)  53.024 ms core52.sto.hetzner.com (213.239.252.238)  53.377 ms  56.688 ms
 9  core31.hel1.hetzner.com (213.239.254.57)  58.300 ms core32.hel1.hetzner.com (213.239.254.69)  58.473 ms core31.hel1.hetzner.com (213.239.254.61)  60.919 ms
10  * * *
11  spine1.cloud1.hel1.hetzner.com (213.239.228.46)  113.817 ms spine2.cloud1.hel1.hetzner.com (213.239.228.50)  64.457 ms spine1.cloud1.hel1.hetzner.com (213.239.228.46)  113.770 ms
12  * * *
13  20188.your-cloud.host (95.216.128.130)  55.064 ms  53.528 ms  53.548 ms
14  archlinux.org (95.217.163.246)  55.362 ms !X  53.135 ms !X  53.000 ms !X

EDIT: I allowed port 67/68 for DHCP and now it's working.

Last edited by proledatarian (2024-08-23 13:43:14)

---

Gitea | AUR-Packages