From: Michael Schachtebeck <schachti@rbw.goe.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: limit extension
Date: Tue, 19 Jul 2005 23:01:21 +0200 [thread overview]
Message-ID: <42DD6A21.3090301@rbw.goe.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0507192209400.16157@yvahk01.tjqt.qr>
Hi.
Am 07/19/2005 10:13 PM schrieb Jan Engelhardt:
> You could use dstlimit with --dstlimit-mode srcip-dstip
> and probably save some rules.
>
> With dstlimit, you also get an overview of which connections are currently
> limited, and their burst status, in /proc/net/ipt_dstlimit/DSTLIMIT_NAME
> It's because I think some burst math allows to have a second packet sneak in.
Won't I have the same problem with it?
According to
http://www.netfilter.org/patch-o-matic/pom-obsolete.html#pom-obsolete-dstlimit,
it's deprecated by hashlimit, but on
http://www.netfilter.org/patch-o-matic/pom-submitted.html#pom-submitted-hashlimit,
I can't find any information on how to use it in my case... Do you know
where to look for it or do you have an example for how to redirect a
single host or a bunch of hosts once a day to the local apache when
trying to make their first http connection, similar to
/sbin/iptables -t nat -I PREROUTING -p tcp -s $IP -i $LAN_DEV --sport
1024: --dport 80 --syn -m limit --limit 1/d --limit-burst 1 -j REDIRECT
--to-port 5000
Michael
--
PGP Public Key: http://www.num.math.uni-goettingen.de/schachte/key.asc
Key fingerprint: C474 8B85 17C0 0232 E439 0FBF 2451 E452 293C D798
next prev parent reply other threads:[~2005-07-19 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 18:07 limit extension Michael Schachtebeck
2005-07-19 20:13 ` Jan Engelhardt
2005-07-19 21:01 ` Michael Schachtebeck [this message]
2005-07-20 6:25 ` Jan Engelhardt
2005-07-20 14:15 ` Michael Schachtebeck
2005-07-20 14:45 ` Sven Schuster
2005-07-20 14:55 ` Michael Schachtebeck
2005-07-20 15:15 ` Sven Schuster
2005-07-20 14:58 ` Sven Schuster
2005-07-20 15:01 ` Sven Schuster
2005-07-20 15:03 ` Michael Schachtebeck
2005-07-20 15:05 ` 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=42DD6A21.3090301@rbw.goe.net \
--to=schachti@rbw.goe.net \
--cc=jengelh@linux01.gwdg.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.