From: Guillermo Chui Lau <memochui@equicomp.com.pe>
To: netfilter@lists.netfilter.org
Cc: tomekm@cea.pl
Subject: RE: transparent proxy
Date: Fri, 27 Feb 2004 14:19:41 -0500 [thread overview]
Message-ID: <6B4345976F8D444ABCFEF8B628BAC1A0431565@APPSRV> (raw)
On Fri, 27 Feb 2004 09:48:39 +0100
"Tomasz Macioszek" <tomekm@cea.pl> wrote:
> Hello!
> I have a Linux server acting as a gateway between internal network and
> internet. The iptables rule set have been working good for long time.
> I have configured squid on this server. When I have set internal network
> client to use directly proxy server it has worked properly. But when I
have
> set iptable to redirect all http traffic to squid port (3128) it didn't
> work (transparent proxy).
> This is my iptable rule:
> iptables -t nat -A PREROUTING -p TCP --dport 80 -j REDIRECT --to-port 3128
> I think that all options in my kernel are set properly.
> I don't know why it doesn't work
> I set tcpdump to listen on 3128 port and when client tried to connect to
web
> server on port 3128 showed only first IP package of this connection and
> connections failed.
> Could you send me a solution for this problem?
> Best regards
> Tomek
>
>
YOU NEED TO IMPLEMENT THIS RULE
iptables -t nat -A PREROUTING -i $LAN_IFACE -p tcp --dport 80 \
-j REDIRECT --to-port 3128
LINUX SERVER HACKS Rob Flickenger
also make squid run in levels 3 ,4 and 5
chkconfig --level 345 squid on
if this doesnt work see if the iptables is doing nat you should have a rule
like this one
iptables -t nat -A POSTROUTING -o $INET_IFACE -j SNAT --to-source $INET_IP
also check if you are loading the modules
/sbin/modprobe ip_tables
/sbin/modprobe ip_conntrack
/sbin/modprobe iptable_filter
/sbin/modprobe iptable_mangle
/sbin/modprobe iptable_nat
/sbin/modprobe ipt_LOG
/sbin/modprobe ipt_limit
/sbin/modprobe ipt_state
you can check the modules using lsmod
Guillermo Chui Lau
Support Enginner
next reply other threads:[~2004-02-27 19:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 19:19 Guillermo Chui Lau [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-09 23:44 transparent proxy 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
2004-03-17 12:33 Fredrik Emil Jensen
2004-03-17 14:21 ` David Cannings
2004-03-15 9:19 Fredrik Emil Jensen
2004-03-16 1:57 ` Alexander Samad
2004-03-16 8:44 ` Antony Stone
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=6B4345976F8D444ABCFEF8B628BAC1A0431565@APPSRV \
--to=memochui@equicomp.com.pe \
--cc=netfilter@lists.netfilter.org \
--cc=tomekm@cea.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox