From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Transparent proxy question
Date: Mon, 15 Mar 2004 10:57:13 +0000 [thread overview]
Message-ID: <200403151057.13169.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <405589BC.70703@stupar.homelinux.net>
On Monday 15 March 2004 10:47 am, Sasa Stupar wrote:
> Antony Stone pravi:
>
> > > $IPT -t nat -A POSTROUTING -o $INIF -s $INNET -d 192.168.10.10 -j SNAT
> > > --to 192.168.10.111
> > >
> > > Is there something to add or change here?
> >
> > Yes. Remove the POSTROUTING rule, because it is specifically changing
> > the source address of all packets sent to the proxy server to be that of
> > the firewall.
>
> Not good. Now my transparent proxy doesn't work anymore. :(
> What's the catch?
1. Now that it isn't working, do you get any errors in your proxy log file, or
does it think there are no requests?
2. What source IPs does your proxy server allow access for?
3. Does the proxy server know how to route back to the clients?
4. Do you have a suitable ESTABLISHED,RELATED rule on your firewall to allow
back the replies? (I expect so, but you didn't post your full ruleset
earlier, so I can't be sure...)
5. Where are the clients on the network in relation to the firewall and the
proxy server (please don't tell me they're on the same subnet as the
proxy...?)
Regards,
Antony.
--
Never write it in Perl if you can do it in Awk.
Never do it in Awk if sed can handle it.
Never use sed when tr can do the job.
Never invoke tr when cat is sufficient.
Avoid using cat whenever possible.
next prev parent reply other threads:[~2004-03-15 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 8:52 Transparent proxy question Sasa Stupar
2004-03-15 9:07 ` Antony Stone
2004-03-15 9:38 ` Sasa Stupar
2004-03-15 10:36 ` Antony Stone
2004-03-15 10:51 ` Sasa Stupar
2004-03-15 11:02 ` Antony Stone
[not found] ` <405589BC.70703@stupar.homelinux.net>
2004-03-15 10:57 ` Antony Stone [this message]
2004-03-15 11:07 ` Sasa Stupar
2004-03-15 11:24 ` Antony Stone
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=200403151057.13169.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox