From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
coreteam@netfilter.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] netfilter: xt_recent: Add optional mask option for xt_recent
Date: Wed, 2 May 2012 02:56:05 +0200 [thread overview]
Message-ID: <20120502005605.GA15074@1984> (raw)
In-Reply-To: <d8de90a8f08a092730109e72827264fe@visp.net.lb>
On Thu, Apr 12, 2012 at 12:00:03PM +0300, Denys Fedoryshchenko wrote:
[...]
> For me personally it is useful, because i have around 140 NAS
> servers, and i give each of them /24 "gray" subnets, and in some
> cases i need to handle bad users, that are changing dynamic ip and
> attacking from new ip each time. I just block non-critical service
> for whole subnet then, till technician on duty will solve issue
> completely. And sure if attack are stopped, subnet will be unblocked
> "automagically".
OK, if you need this, I'm fine with it.
> Sure this feature not critical, or "a must", and if code are not
> good, it is up to you, if it should be added or not.
I didn't say anything about the code yet. E-mail reviewing this will
follow.
next prev parent reply other threads:[~2012-05-02 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 11:24 [PATCH 1/1] netfilter: xt_recent: Add optional mask option for xt_recent Denys Fedoryshchenko
2012-04-11 23:14 ` Pablo Neira Ayuso
2012-04-12 9:00 ` Denys Fedoryshchenko
2012-04-12 9:00 ` Denys Fedoryshchenko
2012-05-02 0:56 ` Pablo Neira Ayuso [this message]
2012-05-02 1:01 ` Pablo Neira Ayuso
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=20120502005605.GA15074@1984 \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=denys@visp.net.lb \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--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.