From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: <netfilter-devel@vger.kernel.org>, Linux netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] iptables: xt_recent: Add optional mask option for xt_recent
Date: Sat, 14 Jul 2012 20:55:57 +0300 [thread overview]
Message-ID: <a2feae54d7bd12b00614e679fd2fd4a9@visp.net.lb> (raw)
In-Reply-To: <20120714150527.GA6271@1984>
Hi Pablo
On 2012-07-14 18:05, Pablo Neira Ayuso wrote:
> Hi Denys,
>
> On Thu, May 17, 2012 at 11:08:57PM +0300, Denys Fedoryshchenko wrote:
>> Use case for this feature:
>> 1)In some occasions if you need to allow,block,match specific
>> subnet.
>> 2)I can use recent as a trigger when netfilter rule matches, with
>> mask 0.0.0.0
>>
>> Tested for backward compatibility:
>> )old (userspace) iptables, new kernel
>> )old kernel, new iptables
>> )new kernel, new iptables
>
> I've cleaned up this patch:
>
>
> http://git.netfilter.org/cgi-bin/gitweb.cgi?p=iptables.git;a=commit;h=73bf03981dfaee48ac1d6da380d46501a96cc83e
>
> It's not yet in master. Please, check that this is correct.
>
> BTW, the man page update is still missing.
Thank you, everything looks ok, i will try to diff(to learn, not repeat
coding style mistakes in next submissions) and test. Since i'm in desert
now, it will take few days.
I will prepare also man page patch for iptables.
---
Denys Fedoryshchenko, Network Engineer, Virtual ISP S.A.L.
next prev parent reply other threads:[~2012-07-14 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 20:08 [PATCH] iptables: xt_recent: Add optional mask option for xt_recent Denys Fedoryshchenko
2012-07-14 15:05 ` Pablo Neira Ayuso
2012-07-14 17:55 ` Denys Fedoryshchenko [this message]
2012-07-29 6:13 ` Denys Fedoryshchenko
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=a2feae54d7bd12b00614e679fd2fd4a9@visp.net.lb \
--to=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 NNTP newsgroup(s).