Linux Netfilter development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ipt_recent misuses jiffies? misreports oldest_pkt too
Date: Thu, 25 Sep 2008 08:02:06 +0200	[thread overview]
Message-ID: <48DB295E.9080102@trash.net> (raw)
In-Reply-To: <iv8md4tqst7jb7j6b3qfokfua9t7qbhth0@4ax.com>

Grant Coady wrote:
> On Thu, 25 Sep 2008 06:46:54 +0200, Patrick McHardy <kaber@trash.net> wrote:
> 
>> Indeed, its completely useless information. Actually I don't see
>> much use for anything in that proc file, but again, I kept it for 
>> compatiblity.
> 
> Twice you mention compatibility, should I plan on a replacement so the 
> old code can be deprecated over time?  The proc file is useful for 
> external timebase process to remove stale IPs or inject IPs for service 
> quota limiting.  (At least, I can see a use for it that way).

The tree I pointed to includes a port of ipt_recent to IPv6 and
adds a new proc file for that. So you could just fix it for the
new proc file, that avoids all compatibility issues.

>> Please base your patches on
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nf-next-2.6.git
> 
> Yeah, me git-challenged ;) got to figure out how to make two trees 
> (this and kernel) play together?  Got the git dribbling in at all of 
> 3k/s (900k objects). 

Its a full tree, so you can simply compile and boot that one.
Or you can pull it into an existing clone of Linus' tree.

      reply	other threads:[~2008-09-25  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25  3:22 ipt_recent misuses jiffies? misreports oldest_pkt too Grant Coady
2008-09-25  4:46 ` Patrick McHardy
2008-09-25  5:51   ` Grant Coady
2008-09-25  6:02     ` Patrick McHardy [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=48DB295E.9080102@trash.net \
    --to=kaber@trash.net \
    --cc=gcoady.lk@gmail.com \
    --cc=netfilter-devel@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