From: Thomas Jacob <jacob@internet24.de>
To: netfilter@lists.netfilter.org
Subject: experiences with ipt_ACCOUNT (was Re: ipt_account / iptables 1.3.8)
Date: Fri, 29 Jun 2007 10:53:12 +0200 [thread overview]
Message-ID: <1183107192.19759.0.camel@localhost> (raw)
In-Reply-To: <4682A981.3090608@plouf.fr.eu.org>
Oh well, thanks for the info. A pity, as in kernels up to 2.6.18
the module was doing its job nicely, but I've now tried it with 2.6.21.5
and
there it doesn't even compile anymore.
There's an alternative module called ipt_ACCOUNT however, where
the docs say that it does support 2.6.21.
==> http://www.intra2net.com/de/produkte/opensource/ipt_account/
I wonder if anyone would like to share experiences with
that particular module in terms of performance and
stability in a 70-100kpps load scenario.
On Wed, 2007-06-27 at 20:16 +0200, Pascal Hambourg wrote:
> Hello,
>
> Thomas Jacob a écrit :
> >
> > It appears that ipt_account has vanished from
> > iptables 1.3.8 (it was still there in 1.3.7) could
> > someone please comment on the why?
> >
> > The changelogs do not mention anything about it
>
> They do, in a rather laconic way though :
>
> <quote>
> - Remove extensions for unmaintained/obsolete patchlets
> </quote>
>
> AFAIK, the concerned extensions are : fuzzy, nth, random (both
> superseded by statistic), ROUTE, account, BALANCE, childlevel,
> connlimit, dstlimit, FTOS, IPMARK, ipv4options, IPV4OPTSSTRIP, mport,
> NETLINK, osf, psd, record_rpc, rpc, TARPIT, TCPLAG, time, TRACE, u32, XOR.
prev parent reply other threads:[~2007-06-29 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 16:43 ipt_account / iptables 1.3.8 Thomas Jacob
2007-06-27 18:16 ` Pascal Hambourg
2007-06-27 18:30 ` David Ford
2007-06-27 18:59 ` Jan Engelhardt
2007-06-27 19:03 ` Jan Engelhardt
2007-06-27 19:39 ` Patrick McHardy
2007-06-27 19:46 ` Jan Engelhardt
2007-06-27 22:15 ` Jozsef Kadlecsik
2007-06-27 23:44 ` Patrick McHardy
2007-06-28 6:43 ` Jan Engelhardt
2007-06-28 11:29 ` Jozsef Kadlecsik
2007-06-29 8:53 ` Thomas Jacob [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=1183107192.19759.0.camel@localhost \
--to=jacob@internet24.de \
--cc=netfilter@lists.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 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.