RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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).