ipt_account / iptables 1.3.8

ipt_account / iptables 1.3.8

[Thomas Jacob]

[-- Attachment #1: Type: text/plain, Size: 316 bytes --]

Hi List,

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, neither
does the source, and also I couldn't find anything
googling thru the mailing list archives.

    T Jacob

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

Re: ipt_account / iptables 1.3.8

[Pascal Hambourg]

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.

experiences with ipt_ACCOUNT (was Re: ipt_account / iptables 1.3.8)

[Thomas Jacob]

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.