From: cc <cc@kdtc.net>
To: Netfilter <netfilter@lists.netfilter.org>
Subject: port 80 redirection
Date: Mon, 11 Aug 2003 18:59:50 +0800 [thread overview]
Message-ID: <3F377726.7060502@kdtc.net> (raw)
Hi,
I'm not sure if this is OT here, but can
someone comment on the following? It is
certainly confusing if not convoluted. There's
always a simple solution, but I'm just
curious as to whether or not such a set
up would work.
I have a LAN beheind a NAT'd firewall
with iptables 1.2.8. Currently,
none of the users are proxied. How
do I transparently proxy the users,
but with their workstations not
needing any proxy changes?
I had an idea, but don't know if
it's do-able (or even should I even
bother)?
ie.
LAN (port 80) ->
IN OUT
->(80 eth1 ) Firewall (eth1 8180)
->(8180 eth0) Proxy Machine (eth0 8181)
->(8181 eth1) Firewall (80 eth0) -> 'Net
So when a packet comes back, it goes :
'Net (port 80) ->
IN Out
->(80 eth0 in) Firewall (eth1 8181)
->(8181 eth0 in) LAN Proxy (eth0 8180)
->(8180 eth1 in) Firewall (eth1 80) -> LAN
This way, I can transparently proxy the users
and I wouldn't need to fiddle around with their
workstation settings.
Any pointers appreciated.
Edmund
next reply other threads:[~2003-08-11 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 10:59 cc [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-14 1:45 port 80 redirection cc
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=3F377726.7060502@kdtc.net \
--to=cc@kdtc.net \
--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