From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Tomasz Macioszek <tomekm@cea.pl>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: transparent proxy
Date: Fri, 27 Feb 2004 06:50:30 -0500 [thread overview]
Message-ID: <1077882630.2140.59.camel@localhost> (raw)
In-Reply-To: <003901c3fd0e$88a3c6f0$2a245cc2@cea05>
On Fri, 2004-02-27 at 03:48, Tomasz Macioszek 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
It has been a while since I set up Squid but I would suggest looking in
a few areas.
Do you really want to redirect all traffic on port 80 or just the
traffic coming in from the internal interface?
Have you allowed traffic to pass on the loopback interface?
I do not recall if one needs to allow traffic to port 3128 on the INPUT
chain.
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2004-02-27 11:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 8:48 transparent proxy 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 [this message]
2004-02-27 17:00 ` Daniel F. Chief Security Engineer -
-- 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-03-15 9:19 Fredrik Emil Jensen
2004-03-16 1:57 ` Alexander Samad
2004-03-16 8:44 ` Antony Stone
2004-02-27 19:19 Guillermo Chui Lau
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=1077882630.2140.59.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--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 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.