Tunneling server for http and https traffic
- From: magnus.moraberg@xxxxxxxxx
- Date: Thu, 21 May 2009 03:37:41 -0700 (PDT)
Hi there,
I have a linux machine which is routed via eth0 to "network A" and via
eth1 to "networkB".
I wish for clients in "network A" to access content on a webserver
located in "network B".
The protocols I wish to support are Http (80) and Https (443).
Firewalls exist between my linux machine and networks A, and between
my linux machine and network B.
I have added networks A and B to my linux machine's routing table and
I can now ping from a machine in network A to the linux machine, and
from the linux machine to the web server on network B.
The firewalls are configured to only accept traffic via port 80 and
443.
So my question is, how do I connect network A and B? I have installed
squid on the linux machine and it is my understanding that if I
configure it as a tunneling server, listening on ports 80 and 443,
that this will achieve what I'm after. Is this correct?
BTW, I am not interested in doing any kind of caching with squid. The
version of squid I have is version 2.5.STABLE.
At the moment the only configuring of squid that I have done is to
have it listen on port 80. When I telnet to the linux machine on port
80 from a machine in network A, I am receiving a squid generated web
page.
Any advice or suggestions are welcome,
Thanks for your help,
Barry
.
- Follow-Ups:
- Re: Tunneling server for http and https traffic
- From: Tauno Voipio
- Re: Tunneling server for http and https traffic
- Prev by Date: Re: IP allocation gateway in subnet
- Next by Date: ICMP and ip prohibit rule
- Previous by thread: Clamav-0.95 with Dansguardian-2.10.0.3 configure problem
- Next by thread: Re: Tunneling server for http and https traffic
- Index(es):
Relevant Pages
|