Red Hat Bugzilla – Bug 1270811
FirewallD prevents Vagrant NFS mounts from working
Last modified: 2016-12-20 09:57:52 EST
Description of problem:
When using Vagrant in Fedora 23, FirewallD prevents Vagrant from sharing a directory between the local Vagrant VM and the host machine. Vagrant uses NFS for this task.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. git clone http://github.com/cockpit-project/cockpit
2. cd cockpit
3. sudo yum install vagrant vagrant-libvirt
4. sudo vagrant up
Hangs for 15 minutes waiting for NFS
Mount succeeds within seconds.
* Workaround is: firewall-cmd --set-default-zone=trusted
* The local virtualization interfaces like virbr0 and virbr1 never have packet filtering for local traffic.
That should say: The local virtualization interfaces like virbr0 and virbr1 *should* never have packet filtering for local traffic.
You could simply set the zone for your bridge devices to trusted in your environment.
Simply allowing any traffic for guests using bridges is not a secure solution. I think it would be bad to make security an opt in feature.
> Simply allowing any traffic for guests using bridges is not a secure solution. I think it would be bad to make security an opt in feature.
Libvirt comes with its own firewall rules for guests. See nwfilter. I don't understand why we need two competing firewalls fighting over libvirt bridges?
Yes, libvirt comes with own rules for guests to be able to make the guests accessible.
I am adding Daniel P. Berrangé to this bug.
Daniel, what is your opinion on this?
(In reply to Thomas Woerner from comment #2)
> You could simply set the zone for your bridge devices to trusted in your
On F22, this doesn't do the trick, unfortunately. See output below
firewall-cmd --list-all --zone=trusted
interfaces: virbr0 virbr1
Despite that, NFS mount hangs on 'vagrant up'
(In reply to Thomas Woerner from comment #4)
> Yes, libvirt comes with own rules for guests to be able to make the guests
> I am adding Daniel P. Berrangé to this bug.
> Daniel, what is your opinion on this?
The host should treat guest OS traffic as if it were malicious, just like it would for any LAN traffic. If the host admin wants to open their host services to permit guest access that should always be an explicit opt-in decision by them IMHO.(In reply to Stef Walter from comment #3)
> > Simply allowing any traffic for guests using bridges is not a secure
> > solution. I think it would be bad to make security an opt in feature.
> Libvirt comes with its own firewall rules for guests. See nwfilter. I don't
> understand why we need two competing firewalls fighting over libvirt bridges?
This does not imply that firewalld should allow guest access to host services by default. The libvirt filters won't even be used by default with typical desktop virt tools like virt-manager, and the default "clean-traffic" provided by libvirt is merely designed to prevent the guest doing IP & MAC address spoofing.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.