From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: port 80 Redirection to differnet ip!!!
Date: Thu, 16 Sep 2004 08:51:37 -0400 [thread overview]
Message-ID: <1095339097.2045.25.camel@wolfpack.ljm.dom> (raw)
In-Reply-To: <a05ad875040916051360d7fe23@mail.gmail.com>
On Thu, 2004-09-16 at 08:13, Murugavel Thiruvengadam wrote:
> hi
>
> I am planning to implement setup like below
>
>
>
> users (all r in public ip) ------> pvt ip linux auth server (nated
> with pub ip in pix)---- pix- bbrouter-- Internet
>
> cache server is lying in the same auth server segment
>
> we are planing to cache all the port 80 traffic so we decided to put
> cache enginee(( ip spoof enabled) on different machine
>
> my question is when ever any dport 80 request come and hit in auth
> server. i want to redirect into cache box without nating source ip.
> bcs if we change the the source ip to cache enginee.
>
> all the request will be generated by cache enginee. i don't want it.
>
> i want to simulate port 80 redirection in L4 switch in iptables.
>
>
> when any port 80 come and hit the auth box just put into the the cache enginee.
>
> The below option will redirect into the same machine
> /sbin/iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT
> --to-port 8080
>
> the below option will change the destation ip and dport
> iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT
> --to-destination 192.168.1:8080
>
> Any suggestion welcome.
it sounds like you want WCCP. google for it and/or take a look at:
http://www.squid-cache.org/WCCP-support/Linux/
there's also a transparent proxy patch in POM (tproxy) that may or may
not be of use to you (i've never tried it).
-j
--
Jason Opperisano <opie@817west.com>
prev parent reply other threads:[~2004-09-16 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 12:13 port 80 Redirection to differnet ip!!! Murugavel Thiruvengadam
2004-09-16 12:51 ` Jason Opperisano [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=1095339097.2045.25.camel@wolfpack.ljm.dom \
--to=opie@817west.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 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.