netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <lists.netfilter@kevin.km6g.us>
To: netfilter@vger.kernel.org
Subject: Re: rate-limit ssh for both IPv4 and IPv6
Date: Wed, 22 Mar 2023 15:27:24 -0400	[thread overview]
Message-ID: <77af66b9-38bd-4f5b-b0b1-f0c063a171e5@app.fastmail.com> (raw)
In-Reply-To: <783937f-4c3b-4520-eb7f-3334ffcdfa0@ndsu.edu>

On Wed, Mar 22, 2023, at 14:28, Tim Mooney wrote:
> With my current experience level with nft, it's not clear to me how to
> adjust a single rule that handles only IPv4 with a set to do what I need
> for both IPv4 and IPv6 connections to ssh.

Do you need to use a single rule? Since the rate-limiting is per-source-address, there's no need to have them mixed together. Two rules, one each for IPv4 and IPv6, with their own sets, should work fine.

       reply	other threads:[~2023-03-22 19:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <783937f-4c3b-4520-eb7f-3334ffcdfa0@ndsu.edu>
2023-03-22 19:27 ` Kevin P. Fleming [this message]
2023-03-22 19:44   ` rate-limit ssh for both IPv4 and IPv6 Tim Mooney
2023-03-22 18:28 Tim Mooney

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=77af66b9-38bd-4f5b-b0b1-f0c063a171e5@app.fastmail.com \
    --to=lists.netfilter@kevin.km6g.us \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).