DUN connections are established by creating and connecting an AF_BLUETOOTH socket.
SELinux does not allow NetworkManager to do that:
Sep 01 13:32:45 rh1 audit[8403]: AVC avc: denied { create } for pid=8403 comm="NetworkManager" scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:system_r:NetworkManager_t:s0 tclass=bluetooth_socket permissive=0
Sep 01 13:32:49 rh1 setroubleshoot[8871]: SELinux is preventing NetworkManager from create access on the bluetooth_socket labeled NetworkManager_t. For complete SELinux messages run: sealert -l b1733272-f75d-4f31-8f6f-746a2957c5f7
Sep 01 13:32:49 rh1 python3[8871]: SELinux is preventing NetworkManager from create access on the bluetooth_socket labeled NetworkManager_t.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that NetworkManager should be allowed create access on bluetooth_socket labeled NetworkManager_t 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 'NetworkManager' --raw | audit2allow -M my-NetworkManager
# semodule -X 300 -i my-NetworkManager.pp
(In reply to Lukas Vrabec from comment #2)
> Hi All,
>
> PR is merged and backported to Rawhide,F31 and F30.
Thank you Lukas,
I think we can close this bug then.
(maybe I should reassign it to SELinux component, but since it's fixed already, there isn't much point).
Closing.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1773
DUN connections are established by creating and connecting an AF_BLUETOOTH socket. SELinux does not allow NetworkManager to do that: Sep 01 13:32:45 rh1 audit[8403]: AVC avc: denied { create } for pid=8403 comm="NetworkManager" scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:system_r:NetworkManager_t:s0 tclass=bluetooth_socket permissive=0 Sep 01 13:32:49 rh1 setroubleshoot[8871]: SELinux is preventing NetworkManager from create access on the bluetooth_socket labeled NetworkManager_t. For complete SELinux messages run: sealert -l b1733272-f75d-4f31-8f6f-746a2957c5f7 Sep 01 13:32:49 rh1 python3[8871]: SELinux is preventing NetworkManager from create access on the bluetooth_socket labeled NetworkManager_t. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that NetworkManager should be allowed create access on bluetooth_socket labeled NetworkManager_t 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 'NetworkManager' --raw | audit2allow -M my-NetworkManager # semodule -X 300 -i my-NetworkManager.pp