All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schachtebeck <schachti@rbw.goe.net>
To: netfilter@lists.netfilter.org
Subject: limit extension
Date: Tue, 19 Jul 2005 20:07:59 +0200	[thread overview]
Message-ID: <42DD417F.4090804@rbw.goe.net> (raw)

Hi,

I'm trying to redirect some people on my router once a day to a local
apache to show them a status page.

I'm using the following iptables rule to redirect them:

/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

At first, I thought everything was fine: I got redirected when trying to
open the first page in my browser, and after that, I could surf normally
without being redirect. But after about 30 minutes, I got redirected
again, and iptables -t nat -vnL PREROUTING said that the rule had
matched twice.

What am I doing wrong? Why was I redirect a second time? In my opinion,
the second redirection should not have happened then, but 1 day (24
hours) later...

Any hint is welcome...

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


             reply	other threads:[~2005-07-19 18:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 18:07 Michael Schachtebeck [this message]
2005-07-19 20:13 ` limit extension Jan Engelhardt
2005-07-19 21:01   ` Michael Schachtebeck
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=42DD417F.4090804@rbw.goe.net \
    --to=schachti@rbw.goe.net \
    --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.