From: Edmundo Carmona <eantoranz@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Squid +iptables + apache
Date: Tue, 20 Sep 2005 08:29:28 -0400 [thread overview]
Message-ID: <65aa6af90509200529591f90dc@mail.gmail.com> (raw)
In-Reply-To: <200509200157.11810.etobis@dc.uba.ar>
what is the error squid reports?
On 9/20/05, Enrique Augusto Tobis <etobis@dc.uba.ar> wrote:
> Hi!
>
> I've been looking for a solution to this problem, but I haven't been able to
> find one. Any ideas?
>
> I have a small home network. I recently set up an old pc as out gateway. I
> have
>
> 192.168.0.3 connecting to the internet, running squid, and acting as the
> firewall/gateway (using nat).
> 192.168.0.1 running apache.
>
> I want to use squid in 192.168.0.3 as a transparent proxy. So far, that works.
> That is, traffic from the 192.168.0.0 network is processed transparently
> by .0.3
>
> I also forwarded connections to port 80 on .0.3 to .0.1, which is running the
> web server. I can successfully access that web server from outside the
> network.
>
> To sum it up, almost everything is working as it should. But, if I try to
> access 192.168.0.3 from INSIDE the network, I get an error from squid...
>
> I activate the transparent proxy with
> iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port
> 8080
>
> and forward the port 80 connections with
> iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT --to 192.168.0.1:80
>
> in that order.
>
> Any ideas?
> Thanks!
> Enrique
>
>
next prev parent reply other threads:[~2005-09-20 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 4:57 Squid +iptables + apache Enrique Augusto Tobis
2005-09-20 12:29 ` Edmundo Carmona [this message]
2005-09-20 13:12 ` /dev/rob0
-- strict thread matches above, loose matches on Subject: below --
2005-09-26 3:41 Squid + iptables " Enrique A. Tobis
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=65aa6af90509200529591f90dc@mail.gmail.com \
--to=eantoranz@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox