Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Firewalld v1.0.0 included breaking changes [1] that affect the libvirt
firewalld backend when using a routed network.
Routed networks worked pre v1.0.0 because of firewalld issue 177 [2].
This was fixed in v1.0.0. Now packets world -> libvirt are blocked.
Assuming we want to address the situation, I think libvirt should use a
firewalld policy to expose the routed VM network.
# firewall-cmd --permanent --new-policy libvirt-fwd-in
# firewall-cmd --permanent --policy libvirt-fwd-in --add-ingress-zone ANY
# firewall-cmd --permanent --policy libvirt-fwd-in --add-egress-zone libvirt
# firewall-cmd --permanent --policy libvirt-fwd-in --set-target ACCEPT
This policy could be shipped similar to the libvirt zone.
Of course, you don't want this policy to go active when using a NAT'd
configuration. To control that the shipped policy could omit the
egress-zone (making it inactive) and libvirt only adds it at runtime for
routed networks.
[1]: https://firewalld.org/2021/06/the-upcoming-1-0-0 "Default target is now similar to reject"
[2]: https://github.com/firewalld/firewalld/issues/177
Comment 2yalzhang@redhat.com
2023-07-24 03:36:12 UTC
Test on libvirt-9.5.0-3.el9.x86_64, the issue is fixed.
Refer to bug 2055706#c3 for the test steps.
Comment 3yalzhang@redhat.com
2023-07-24 04:43:16 UTC
Test on libvirt-9.5.0-3.el9.x86_64, the issue is fixed.
1. Prepare and start a network with forward mode='route':
# virsh net-dumpxml route
<network>
<name>route</name>
<uuid>ad814f81-3ffe-4f3b-b662-1e997a524156</uuid>
<forward mode='route'/>
<bridge name='virbr1' stp='on' delay='0'/>
<mac address='52:54:00:4e:26:38'/>
<ip address='192.168.100.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.100.2' end='192.168.100.254'/>
</dhcp>
</ip>
<ip family='ipv6' address='2001:db8:ca2:2::1' prefix='64'>
<dhcp>
<range start='2001:db8:ca2:2::10' end='2001:db8:ca2:2::ff'/>
</dhcp>
</ip>
</network>
2. Start a vm with network type interface connected to this network;
3. On a remote host which can access to this local host, add a route like as below:
# ip route add 192.168.100.0/24 dev eno1 via ${ip_of_local_host}
4. On remote host, ping guest(both ipv4 and ipv6), succeed;
5. On guest, ping the remote host(both ipv4 and ipv6), succeed;
Comment 4yalzhang@redhat.com
2023-07-24 04:46:01 UTC
Hi Laine, as the test results in comment 3 and what you have confirmed on bug 2055706#c5, I think we can close this bug as "current release".
What do you think? Thank you!