From: trentbuck@gmail.com (Trent W. Buck)
To: netfilter@vger.kernel.org
Subject: Re: nftables
Date: Thu, 30 Apr 2020 13:52:56 +1000 [thread overview]
Message-ID: <87imhhvdd3.fsf@goll.lan> (raw)
In-Reply-To: 16ac0a06-b73e-dd66-c858-ae9ea26034d6@gmail.com
Fatih USTA <fatihusta86@gmail.com> writes:
> You can use sets in nftables like iptables ipset.
> http://wiki.nftables.org/wiki-nftables/index.php/Sets
See also sshguard[1] or fail2ban, for turnkey Intrusion Prevention Systems
(i.e. "block attackers by IP address").
Their nft-specific code is not very interesting:
https://bitbucket.org/sshguard/sshguard/src/master/src/fw/sshg-fw-nft-sets.sh
https://github.com/fail2ban/fail2ban/blob/bb0f732ae69894b22306dd7efa213513e3acd8a2/config/action.d/nftables.conf
[1] don't be fooled by the name; sshguard also handles postfix, dovecot, and NCSA (nginx/apache).
next prev parent reply other threads:[~2020-04-30 3:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 7:38 nftables Patrick Greiff
2020-04-28 7:50 ` nftables Fatih USTA
[not found] ` <169e18be-82c8-47b7-2ca6-44e03c86eebd@gmx.de>
2020-04-28 8:45 ` nftables Fatih USTA
2020-04-30 3:52 ` Trent W. Buck [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-05 7:24 nftables Juraj Gabčík
[not found] <BANLkTikT_ETuEE2e7Khip9xJKFiDgBe7Qg@mail.gmail.com>
2011-04-29 9:33 ` Fwd: nftables Juraj Gabčík
2011-04-29 10:06 ` nftables Jan Engelhardt
[not found] <4976FF54.1000009@linux.vnet.ibm.com>
[not found] ` <200901271540.36749.rusty@rustcorp.com.au>
[not found] ` <497ED2B5.4040703@trash.net>
[not found] ` <497F059F.7070903@linux.vnet.ibm.com>
[not found] ` <497F09CA.2040306@trash.net>
[not found] ` <497FEBE5.1050508@linux.vnet.ibm.com>
[not found] ` <498013D7.3010401@trash.net>
[not found] ` <49C083F4.9010506@linux.vnet.ibm.com>
[not found] ` <49C089A2.2020809@trash.net>
[not found] ` <49C09610.1010106@linux.vnet.ibm.com>
2009-03-18 7:47 ` nftables Patrick McHardy
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=87imhhvdd3.fsf@goll.lan \
--to=trentbuck@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.