Comment # 3 on bug 1226105 from Alexander Graul

I have the same issue. Existing or new VMs alike can't communicate to external
hosts, e.g.:

localhost:~ # tracepath suse.com
 1?: [LOCALHOST]                      pmtu 1500
 1:  192.168.122.1                                         0.159ms 
 1:  192.168.122.1                                         0.077ms 
 2:  no reply
 3:  no reply

The VM has the following network configuration:
localhost:~ # ip a
[ skipping lo device ]
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
    link/ether 52:54:00:2d:e6:f1 brd ff:ff:ff:ff:ff:ff
    altname enp1s0
    inet 192.168.122.40/24 brd 192.168.122.255 scope global dynamic
noprefixroute eth0
       valid_lft 2946sec preferred_lft 2946sec
    inet6 fe80::5054:ff:fe2d:e6f1/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
localhost:~ # ip r
default via 192.168.122.1 dev eth0 proto dhcp src 192.168.122.40 metric 20100 
192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.40 metric 100 

`virsh domifaddr test-slem5` reports the same from the host (running 20240609). 

I'm running the modular deamons (libvirtd.service is not running) and will
attach the output of `virsh dumpxml test-slem5` and `virsh net-dumpxml
default`. I also tried other NAT networks I have defined, with the same result
(all packets are dropped, tracepath only shows one hop to the hypervisor).

Please let me if there is anything else I can share to track this down.