When exactly will the build service pull this change? It is supposed to notice changes automatically, right?
Now that the change is in Tumbleweed I notice that the behaviour of systemctl start nftables.service is still a bit unfortunate. Even if the service is not configured (config file condition…
I incorporated your suggestions and some other fixes
A thanks for forwarding that to upstream. No reaction so far, though, it seems.
Placing config files in /usr/etc when they are not read from that location also seems a bit strange; traditionally (open)SUSE would put such files in %_docdir instead.
True. This whole…
- the Netfilter wiki casually puts the ruleset in /etc/nftables.rules and /etc/nftables/*
- Arch…
I'm not throwing in the towel, I'm fulfilling a customer request. I looked at what other distributions do. This here is not perverting an upstream approach, it is filling a gap. I can approach…
I can add a Conflicts= statement to the systemd unit to prevent accidental activation of both this service and firewalld. SUSEFirewall is not a candidate here since it is deprecated and doesn't…
It's not colliding, because it is the responsibility of the system admin not to use both at the same time. And we do have a customer request to add this service.