All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Whinnery <martin.whinnery@sbirmc.ac.uk>
To: netfilter@lists.netfilter.org
Subject: transparent proxy with captive page - ipt_recent?
Date: Mon, 25 Jun 2007 16:40:20 +0100	[thread overview]
Message-ID: <467FE1E4.2040306@sbirmc.ac.uk> (raw)

Hi,

Here's what I'm trying to do:

I've got a gateway box, running squid on port 8080, and apache on port 82.

I've got transparent proxying working fine, using a redirect rule in the 
prerouting table.

What I'd like to do is, the first time a web connection from IP 'n' 
comes in, they get a page from apache, telling users a proxy address 
they may want to set, in which case they'll get https proxying etc.

But if they don't bother, I'd like further web requests redirected to 
the proxy for transparent proxying, until a certain amount of idleness 
has gone by, when we revert to the local page again.


So everyone gets proxy instructions when they start browsing, and the 
lazy ones get transparent proxying.

I thought I could do this with ipt_recent, but it's not happening.

Here's me rules:

/sbin/iptables -t nat -A PREROUTING -p tcp --dport 80 -m recent --rcheck 
--seconds 30 -j REDIRECT --to-ports 8080
/sbin/iptables -t nat -A PREROUTING -p tcp --dport 80 -m recent --set -j 
REDIRECT --to-ports 82

So I thought the first rule wouldn't match first time around. Then the 
second rule would provide the proxy instructions page, and make the 
/proc/sys/net/ipt_recent/DEFAULT entry. This works fine.

But the first rule should match on the next request. And it doesn't seem 
to. And I don't understand.

Any thoughts?

Mart

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



             reply	other threads:[~2007-06-25 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 15:40 Martin Whinnery [this message]
2007-06-26  7:43 ` transparent proxy with captive page - ipt_recent? Martijn Lievaart
2007-06-26  8:12   ` Martin Whinnery

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=467FE1E4.2040306@sbirmc.ac.uk \
    --to=martin.whinnery@sbirmc.ac.uk \
    --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.