All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Leach <raymondl@knowledgefactory.co.za>
To: netfilter EMAIL <netfilter@lists.netfilter.org>
Subject: Re: more fun with squid
Date: 12 May 2003 08:12:10 +0200	[thread overview]
Message-ID: <1052719930.1460.5.camel@raylinux.internal> (raw)
In-Reply-To: <ABEKJILKOKKGGDJKHKDFOEPICAAA.patrick@vikus.com>

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

Hi

To set squid up as a transparent proxy (obviously read the HowTo for
this), and basically there are 4 directives to change in the config
file:

httpd_accel_uses_host_header on
httpd_accel_port 80
httpd_accel_host virtual
... umm the last only is something like httpd_accel_proxy....something

Then you have to get netfilter to redirect packets to squid:

iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to
1.2.3.4:3128




On Fri, 2003-05-09 at 21:49, Patrick Ahler wrote:
> Ok, I got squid working great behind my firewall even set it up so IE would
> autodetect it. What I would rather do though is have netfilter/the firewall
> server(192.168.1.a) forward any http packets from my network 192.168.1.0 to
> the proxy server on 192.168.1.b and then out to the internet through the
> firewall(192.168.1.a). That way the proxy would be transparent to the users'
> browsers and no autodetection would be required. Not sure how to setup these
> rules, or if this is even the most efficient way of accomplishing the task.
> Also, I don't know if it makes a difference... but the firewall runs NAT
> tables.
> 
> So, in other words, this is what I'd like to do...
> (user)192.168.1.c --->(firewall)192.168.1.a--->(squid/proxy)192.168.1.b--->(
> firewall)192.168.1.a
> 
> Thanks in advance,
> -Patrick
> 
> 
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-05-12  6:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 19:49 more fun with squid Patrick Ahler
2003-05-09 20:58 ` Aldo Lagana
2003-05-12  6:12 ` Ray Leach [this message]

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=1052719930.1460.5.camel@raylinux.internal \
    --to=raymondl@knowledgefactory.co.za \
    --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.