It loads, does it’s stuff (reads the configuration stored in the /etc/nftables.conf file) and goes inactive. nftables.service will load rules from that file when started or enabled. simple
So and how I can monitor that its actually working? I mean without trying bypassing firewall.
I was stand for that if its the systemd service then it should work all the time.
In this case could you explain how its actually work, who is responsible for it? If its not demon then what is that? Archwiki says start and enable service it doesn’t tell that service shouldn’t be active.
@ishaanbhimwal oh thank you, that thread makes it clear. Its new behavior according to
Edit: Downgrading nftables from 1:0.9.9-6 to 1:0.9.9-1 seems to fix it for now…
I was think I’m out of mind cuz I clearly remember previously service was active and running and today I just accidentally notice that service is dead.
@webcaptcha You got it wrong as did the OP of the reddit thread.There is nothing wrong with nftables. See the pinned comment please.
Doesn’t matter. Nftables is not a daemon; it’s a .service that uploads your rules into the kernel and goes off. There’s no “nftablesd” process that inspects your traffic, the kernel does that on its own.
