All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List
	<netfilter-devel@lists.netfilter.org>,
	kadlec@blackhole.kfki.hu
Subject: Re: xt_TARPIT (was: ipt_account / iptables 1.3.8)
Date: Mon, 09 Jul 2007 17:04:20 +0200	[thread overview]
Message-ID: <46924E74.1060706@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707091654180.32335@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Jul 9 2007 16:15, Patrick McHardy wrote:
> 
>>>>No, I couldn't come up with a good way to remove the xrlim abuse yet.
>>>>
> 
> 
> If you ask me, just remove the xrlim call, and replace it by
> some sort of 'last' timestamp, e.g.
> 
> time_t last;
> 
> static int target()
> {
> 	if (!otcph->syn && otcph->ack)
> 		if (!(last <= now() + 5))
> 			return; /* rate limit */
> 	last = now();
> }

The difference is that this is a global ratelimit, while xrlim_allow
is a per dst_entry ratelimit.

> As far as I can see, that xrlim call is there for at least one case:
> 
> tarpit sends ACKs with window=0, but client ignores the RFC-given delay for
> window=0 packets.


I think its more to prevent flooding your upstream, especially with
asynchronous bandwidth. Same reason you would usually rate-limit
the REJECT target on a DSL line.

  reply	other threads:[~2007-07-09 15:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 14:59 xt_TARPIT (was: ipt_account / iptables 1.3.8) Jan Engelhardt
2007-07-09 13:37 ` Patrick McHardy
2007-07-09 14:11   ` Jan Engelhardt
2007-07-09 14:15     ` Patrick McHardy
2007-07-09 14:58       ` Jan Engelhardt
2007-07-09 15:04         ` Patrick McHardy [this message]
2007-07-09 15:09           ` Jan Engelhardt
2007-07-09 15:16             ` Patrick McHardy
2007-07-10  9:17               ` Jan Engelhardt
     [not found] ` <20070710190717.ccq5x5v4s5pqvxto@m.safari.iki.fi>
2007-07-18 11:12   ` Jan Engelhardt
2007-07-18 13:04     ` Patrick McHardy
2007-07-18 15:02       ` Jozsef Kadlecsik
2007-07-19  0:38         ` xt_TARPIT Yasuyuki KOZAKAI
2007-07-19  0:44           ` xt_TARPIT Patrick McHardy
2007-07-19  1:09             ` xt_TARPIT Yasuyuki KOZAKAI
2007-07-19  6:49             ` xt_TARPIT Jozsef Kadlecsik
2007-07-29 14:44               ` xt_TARPIT Jan Engelhardt
2007-07-30 12:23                 ` xt_TARPIT Patrick McHardy
2007-07-30 13:35                   ` xt_TARPIT Jan Engelhardt

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=46924E74.1060706@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@computergmbh.de \
    --cc=kadlec@blackhole.kfki.hu \
    --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.