Hello
When I boot my shiny Fedora Server 43 , network interfaces are DOWN.
I’ve discovered it’s due to SELinux not allowing NetworkManager creating files below /run, so doing sudo setenforce permissive solves the issue
What I’m very surprised nobody has realized this before me…am I missing something??
Thanks a lot!
P.S: I’ll put my findings here:
journalctl -p err -e output:
`Nov. 04 09:27:01 localhost systemd[1]: Failed to start NetworkManager.service - Network Manager.`
`Nov. 04 09:27:03 localhost setroubleshoot[741]: SELinux is preventing NetworkManager from read access in file 10-globally-managed-devices.conf. For full SELinux messages run: sealert -l efbd8d52-bc6a-45d0-89d6-a5b517d3c7bb`
`Nov. 04 10:07:43 localhost setroubleshoot[1195]: failed to retrieve rpm info for path ‘/run/NetworkManager/conf.d/10-globally-managed-devices.conf’:`
`Nov. 04 10:07:43 localhost setroubleshoot[1195]: failed to retrieve rpm info for path ‘/run/NetworkManager/system-connections/netplan-enp0s3.nmconnection’:`
`Nov. 04 10:07:43 localhost setroubleshoot[1195]: SELinux is preventing NetworkManager from read access on file netplan-enp0s3.nmconnection.For full SELinux messages run: sealert -l 58e4549e-473f-43be-90bd-a7138dec5868`
sealert -l efbd8d52-bc6a-45d0-89d6-a5b517d3c7bb output:
`SELinux is preventing NetworkManager from read access to file 10-globally-managed-devices.conf.`
`***** The catchall plugin (with 100% confidence) suggests ************`
`If you believe that NetworkManager should be allowed read access to file 10-globally-managed-devices.conf by default.Then you should report this as a bug.You can generate a local policy module to allow this access.Do allow it for now by running:`
`ausearch -c ‘NetworkManager’ --raw | audit2allow -M my-NetworkManager`
`semodule -X 300 -i my-NetworkManager.pp`