Description of problem: Not at all sure what the root cause was but systemd-resolved 233 got multicast DNS support which uses port 5353 SELinux is preventing systemd-resolve from 'name_bind' accesses on the udp_socket port 5353. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-resolve should be allowed name_bind access on the port 5353 udp_socket by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'systemd-resolve' --raw | audit2allow -M my-systemdresolve # semodule -X 300 -i my-systemdresolve.pp Additional Information: Source Context system_u:system_r:systemd_resolved_t:s0 Target Context system_u:object_r:howl_port_t:s0 Target Objects port 5353 [ udp_socket ] Source systemd-resolve Source Path systemd-resolve Port 5353 Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-241.fc26.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.11.0-0.rc0.git9.1.fc26.x86_64 #1 SMP Fri Mar 3 16:57:16 UTC 2017 x86_64 x86_64 Alert Count 4 First Seen 2017-03-08 00:02:46 EET Last Seen 2017-03-08 22:05:54 EET Local ID dc12e125-4eb2-4bee-b889-ebe9a284a347 Raw Audit Messages type=AVC msg=audit(1489003554.782:518): avc: denied { name_bind } for pid=12303 comm="systemd-resolve" src=5353 scontext=system_u:system_r:systemd_resolved_t:s0 tcontext=system_u:object_r:howl_port_t:s0 tclass=udp_socket permissive=1 Hash: systemd-resolve,systemd_resolved_t,howl_port_t,udp_socket,name_bind Version-Release number of selected component: selinux-policy-3.13.1-241.fc26.noarch Additional info: component: selinux-policy reporter: libreport-2.9.0 hashmarkername: setroubleshoot kernel: 4.11.0-0.rc0.git9.1.fc26.x86_64 type: libreport
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.