From: "François Patte" <francois.patte@gmx.fr>
To: Reindl Harald <h.reindl@thelounge.net>, netfilter@vger.kernel.org
Subject: Re: unable to start nftables
Date: Sat, 12 Aug 2023 18:53:03 +0200 [thread overview]
Message-ID: <2d987f2b-a910-05d3-c69f-809697cce2f0@gmx.fr> (raw)
In-Reply-To: <72f1558f-2c2d-4bc2-5138-de31c9ae8f40@thelounge.net>
Le 12/08/2023 à 18:41, Reindl Harald a écrit :
>
>
> Am 12.08.23 um 18:36 schrieb François Patte:
>> Le 12/08/2023 à 18:29, Reindl Harald a écrit :
>>>
>>>
>>> Am 12.08.23 um 17:18 schrieb François Patte:
>>>> Bonjour,
>>>>
>>>> I am currently unable to start nftables service, the answer is:
>>>>
>>>> internal:0:0-0: Error: Could not open file
>>>> "/etc/sysconfig/nftables.conf": Permission denied
>>>>
>>>> file /etc/sysconfig/nftables.conf exists and have 755 permissions.
>>>>
>>>> What can I do?
>>>
>>> sounds like SELinux / AppAmor problem - that's why you should provide
>>> informations about your system - we don't even know your distribution
>>> nor do you provide your service unit or even the init-system
>>
>> system is fedora 36
>
> EOL since 2023‑05‑16 which is *3 months ago*
> F37 was released 2022-11-16
> it's time to plan upgrade to F38 currently
>
> don't run a bleeding edge distro when you can't cope with updates!
It is a server at ovh and they installed this version... Now they
propose f38, I'll upgrade.
>
>> selinux policy is enforced
>> nftables is enabled
>>
>> And yes, it is a selinux problem: if I setenforce to 0, I can start
>> nftables (but I found this solution after posting....)
>>
>> I can go back to setenforce 1 without annoying nftables but, the problem
>> remains if I reboot the machine.
>
> Google: "fedora restore selinux context of a specific file"
>
> https://www.thegeekstuff.com/2017/05/restorecon-examples/
Thank you, this solved the problem.
F.P.
prev parent reply other threads:[~2023-08-12 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 15:18 unable to start nftables François Patte
2023-08-12 16:29 ` Reindl Harald
2023-08-12 16:36 ` François Patte
2023-08-12 16:41 ` Reindl Harald
2023-08-12 16:53 ` François Patte [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d987f2b-a910-05d3-c69f-809697cce2f0@gmx.fr \
--to=francois.patte@gmx.fr \
--cc=h.reindl@thelounge.net \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).