Description of problem:
Have a libvirt(own dhcp) with network in forward=route mode on a box directly connected to the internet with masquerade, all on the same one box.
I failed to block/ban traffic between a guest & the Internet. I've tried rich & direct.
It is either libvirt that puts it's rules that high up or firewalld not having _direct going in as first and foremost, or both libvirt and firewalld having it wrong?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Yes, libvirt is pushing it's own rules in the beginning, there is not a lot that firewalld could do here. This needs to be addressed in libvirt.
Reassigning to libvirt.
If you're trying to control access for guests, then you should not be using firewalld directly, instead use libvirt's network filter facility which lets you attach filtering rules to guest virtual NICs. This is documented here http://libvirt.org/formatnwfilter.html
I cannot see a bug to be fixed. I would recommend using the libvirt-users mailing list for general questions like this one. Thank you.
fist of all it should be in man pages - we should not have to (first) go to any mailing list. Is it there?
I would hope - this would not be pipe's dream - that libvirt one day could give us a nicely formated & comprehensive man pages, maybe something what systemd & firewall does - libvirtd.formatfilter, etc. - users/admins should not have to sroogle, man pages is (should always be) the place.
Secondly, I filed it as firewall's problem - which to me was (possibly a bug) because it is unable to control the traffic between VM guest and the rest (Internet in my case).