All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	David Ford <david@blue-labs.org>
Subject: Re: ipt_account / iptables 1.3.8
Date: Wed, 27 Jun 2007 21:39:37 +0200	[thread overview]
Message-ID: <4682BCF9.6040100@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0706272059590.11120@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> Uhm, please add a reference next time; only by chance I found the thread origin
> at the netfilter@ list.
>
> No idea why TARPIT got removed. Maybe it's "unmaintained", but it did not need
> a lot of maintenance either. Though, people had to patch their kernel.
>
> There is no replacement for TARPIT - it's solid. (And xt_DELUDE does not
> replace it; it is something inbetween REJECT and TARPIT.)


Maintenance is only one aspect, but it is a problem since we can't
even compile test it without patching our kernels. A second problem
with most of these matches and targets is that they usually have a
broken non-64 bit clean ABI and if we decide to merge them someday
we need to fix that and thereby break compatibility before it was
even included in the kernel, which is ridiculous.

They should have never gotten into a release and we fixed that now.
You can still patch your kernel and iptables as you like.

  reply	other threads:[~2007-06-27 19:39 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 [this message]
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   ` experiences with ipt_ACCOUNT (was Re: ipt_account / iptables 1.3.8) Thomas Jacob

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=4682BCF9.6040100@trash.net \
    --to=kaber@trash.net \
    --cc=david@blue-labs.org \
    --cc=jengelh@computergmbh.de \
    --cc=netfilter-devel@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.