Control: fixed -1 0.9.0-1
On Fri, 23 Nov 2018 08:52:01 +0100 Gert wrote:
> After analyzing my config, I can now give a full example.
> The subnet came from a geoblock list, the separate host came from an
> abusers list.
> That causes the conflict in Buster (which can be fixed with auto-merge).
After analyzing my config, I can now give a full example.
The subnet came from a geoblock list, the separate host came from an
abusers list.
That causes the conflict in Buster (which can be fixed with auto-merge).
And I tried it again on a different Stretch machine, and it indeed works
fine.
Whoops, the "System Information" is not from the affected system, but
from the system I used to write the report. So ignore that.
System Information from the affected system:
linux-image-4.18.0-2-amd64 4.18.10-2+b1
nftables 0.9.0-1
libnftables0 0.9.0-1
libnftnl7 1.1.1-1
libxtables12 1.8.2-2
Package: nftables
Version: 0.9.0-1
Severity: normal
Hi,
I make use of a "named set" for blacklisting purposes.
The relevant part in /etc/nftables.conf:
table ip filter {
set blacklist {
type ipv4_addr
flags interval
include
4 matches
Mail list logo
