Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Perry Thompson <contact@ryper.org>
To: Martin Bednar <martin@serafean.cz>
Cc: netfilter@vger.kernel.org
Subject: Re: recent module in nftables
Date: Sun, 30 Jul 2017 18:32:04 -0500	[thread overview]
Message-ID: <20170730183152.12d8a637@lustre.ryper.org> (raw)
In-Reply-To: <1889595.mTRbqK2Shg@ged>

[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]

Thank you. I hadn't known about hashlimits and flow. While it is still
a bit different, this will work perfectly for what I need it to do.

I suppose from here I'd be curious to know if the "recent" module has
any benefits over "hashlimit" in iptables, and I suppose I'm still
curious to know if it plans on being implemented in nftables or left
out completely, if anyone knows.

Thank you,

On Fri, 28 Jul 2017 21:57:25 +0200
Martin Bednar <martin@serafean.cz> wrote:

> On Thursday, 27 July 2017 22:59:59 CEST Perry Thompson wrote:
> > Hello all,
> > 
> > It may be way to early to ask this question, but I thought I might
> > as well see if anyone has any information on it.
> > 
> > Will the "recent" module or an option with a similar function be
> > introduced into nftables in the future? Are there any plans to
> > create something like this? It has always been a very good tool for
> > keeping bad IPs from touching my system.  
> 
> I think flow tables might fit the bill.
> https://wiki.nftables.org/wiki-nftables/index.php/Flow_tables
> 
> I use them for filtering out SSH connection attempts, by allowing 3
> SYN packets per minute.
> 
> tcp dport ssh ct state new flow table ssh { iif . ip saddr . tcp
> dport timeout 1h limit rate 3/minute}  accept
> 
> 
> Cheers
> 
> Martin.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-07-30 23:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 20:59 recent module in nftables Perry Thompson
2017-07-27 21:46 ` /dev/rob0
2017-07-27 22:18   ` James
2017-07-28 19:57 ` Martin Bednar
2017-07-30 23:32   ` Perry Thompson [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=20170730183152.12d8a637@lustre.ryper.org \
    --to=contact@ryper.org \
    --cc=martin@serafean.cz \
    --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