Bug 905293 - firewall configurability regression
firewall configurability regression
Status: CLOSED DUPLICATE of bug 903456
Product: Fedora
Classification: Fedora
Component: firewalld (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Thomas Woerner
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-01-29 00:06 EST by Andrei Gaponenko
Modified: 2013-01-29 06:24 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-01-29 06:24:18 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrei Gaponenko 2013-01-29 00:06:04 EST

To allow (KVM) virtual machine guests running on a Fedora 16 host
connect to host services one could open system-config-firewall, define
"virbr0" and "vnet0" as trusted interfaces, and be done.

On Fedora 18, the firewall-config GUI does not provide any means to
work with network interfaces.  Moreover,

# firewall-cmd --zone=trusted --add-interface=virbr0
# firewall-cmd --zone=trusted --add-interface=vnet0

works, but only until the next host reboot, while

# firewall-cmd  --permanent --zone=trusted --add-interface=virbr0
# firewall-cmd  --permanent --zone=trusted --add-interface=vnet0

just brings up a man page (no error message???)
This is firewalld-0.2.12-1.fc18.src.rpm


PS. I am aware of #882736, which reports that the patch to firewalld
allows to restore VM guest functionality by setting default zone to
"trusted".  That workaround is unsatisfactory because of its potential
to create security problems.
Comment 1 Jiri Popelka 2013-01-29 06:24:18 EST

*** This bug has been marked as a duplicate of bug 903456 ***

Note You need to log in before you can comment on or make changes to this bug.