Most people use masquerade/NAT for this. If your OS is capable of
transparent proxying then it is most likely also capable of
masquerade/NAT.
Squid cannot be used for "transparent SSL" proxying.
-- Henrik Nordstrom Squid Hacker Kenneth Stephen wrote: > I have come across posts to the squid mailing lists on this topic circa > 1999. The statements I've seen made on this topic can be summarized as : > "Why do you want to do this - there is no benefit to caching SSL > traffic". > > Well - I do _not_ want caching. Nevertheless I do need a transparent > proxy that can handle SSL. Let me explain : > > I have a private network (ip address range of 192.168.0.*) in a lab > with each ip-address running a proxy server on it. Naturally, the router > doesnt allow traffic for 192.168.0.* into or out of the lab. I was > hoping that with a transparent proxy running on the router, the http > traffic could be correctly served to machines external to the lab - i.e. > the transparent proxy would make the requests to the proxy servers > running on the private ip addresses on behalf of the clients outside the > lab. Now, from reading the docs, there seems to be no problem to > implementing it with http. However, it is not clear to me that this is > possible with https. Is this possible with squid? Is there a better > solution to my problem that doesnt involve using squid? Any help would > be appreciated. > > Thanks in advance, > Kenneth StephenReceived on Sat Apr 28 2001 - 12:25:14 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:59:39 MST