Bug 1339010 - NetworkManager dnsmasq fails to work with SELinux enabled, breaking network connectivity
Summary: NetworkManager dnsmasq fails to work with SELinux enabled, breaking network c...
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 24
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2016-05-23 22:58 UTC by Adam Williamson
Modified: 2017-08-08 14:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-08 14:37:44 UTC
Type: Bug

Attachments (Terms of Use)

Description Adam Williamson 2016-05-23 22:58:48 UTC
I have this in /etc/NetworkManager/NetworkManager.conf:


the 'dns' line there tells it to run dnsmasq as a local caching nameserver. With recent F24 updates, this is broken. When I boot the system, dnsmasq is running but no name resolution works. In the logs I see:

May 23 15:51:54 adam.happyassassin.net NetworkManager[1267]: <warn>  [1464043914.9449] dnsmasq[0x560e674fc2e0]: dnsmasq update failed: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender=":1.9" (uid=0 pid=1267 comm="/usr/sbin/NetworkManager --no-daemon ") interface="org.freedesktop.NetworkManager.dnsmasq" member="SetServersEx" error name="(unset)" requested_reply="0" destination=":1.30" (uid=0 pid=1821 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground")

If I do 'setenforce Permissive' then restart NetworkManager, dnsmasq comes up working and I get name resolution again.

[root@adam /]# rpm -q dnsmasq NetworkManager selinux-policy-targeted

Comment 1 Fedora Admin XMLRPC Client 2016-09-27 15:07:02 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora End Of Life 2017-07-25 20:52:27 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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'
of '24'.

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

Comment 3 Fedora End Of Life 2017-08-08 14:37:44 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.

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