All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Samad <alex@samad.com.au>
To: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: transparent proxy
Date: Tue, 16 Mar 2004 12:57:24 +1100	[thread overview]
Message-ID: <20040316015724.GF26800@samad.com.au> (raw)
In-Reply-To: <3C204966522884458700FF59D6EFB87A474DDE@FORUS01.netpower.lan>

[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]

On Mon, Mar 15, 2004 at 10:19:35AM +0100, Fredrik Emil Jensen wrote:
> Hey 
> 
> I'm currently using squid and squidGuard for redirection. Setting up the
> rules:
> 
> Iptables -t nat -A PREROUTING -p tcp -s 192.168.1.0/24 -d 0/0 --dport 80
> -j REDIRECT --to-ports 3128 
> 
> But does anyone know what to do if you want to use iptables to bypass
> squid with single IP address?
> 
> I know that you can add the rule "iptables -t nat -A POSTROUTING -o eth0
> -s 192.168.1.10/32 -d 0/0 -j SNAT --to "source_Wan_address" ". But this
> rule will be added at the end of the rule list, and all traffic on port
> 80 will still be redirected through squid. Even when I use priority
> "iptables -t nat -I POSTROUTING 1 etc" and I put higher priority on the
> rule for the bypass IP, it is still being redirected through squid. I
> have to remove the redirect rule before I can bypass squid. 

-A means to append to the end of the chain
-I means to insert at the top
or

-I INPUT 5 - mean to insert above line 5 of a chain.

Chains a processed from top to bottom 

hope that helps


> 
> Does anyone know what I'm doing wrong?
> 
> Using Slackware 9.1 with Kernel 2.6.2, iptables version 1.2.9 and squid
> 2.5
> 
> Regards, 
> Fredrik
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-03-16  1:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15  9:19 transparent proxy Fredrik Emil Jensen
2004-03-16  1:57 ` Alexander Samad [this message]
2004-03-16  8:44 ` Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2010-03-09 23:44 Marco Schuth
2010-03-10  0:23 ` Amos Jeffries
2010-03-13  8:21   ` Mart Frauenlob
2010-03-13 10:05     ` /dev/rob0
2010-03-13 12:08       ` Mart Frauenlob
2010-03-13 12:11         ` Mart Frauenlob
2010-03-13 16:41         ` /dev/rob0
2010-03-13 21:58           ` Mart Frauenlob
2005-02-03 12:30 Luca Ferrari
2005-02-03 15:58 ` Jens Knoell
2005-02-05 18:22   ` Andreas Unterkircher
2005-02-05 19:42     ` Adrian C.
2005-02-05 20:22       ` Andreas Unterkircher
2005-02-05 20:47         ` Andreas Unterkircher
2004-03-17 12:33 Fredrik Emil Jensen
2004-03-17 14:21 ` David Cannings
2004-02-27 19:19 Guillermo Chui Lau
2004-02-27  8:48 Tomasz Macioszek
2004-02-27  9:18 ` Jeroen Vriesman
2004-02-27  9:27   ` Antony Stone
2004-02-27 10:25     ` Jeroen Vriesman
2004-02-27 11:50 ` John A. Sullivan III
2004-02-27 17:00 ` Daniel F. Chief Security Engineer -
2003-09-10 21:19 Transparent Proxy Kilson Arruda
2002-11-25 13:04 Cyril COUPEL

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=20040316015724.GF26800@samad.com.au \
    --to=alex@samad.com.au \
    --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.