From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martijn Lievaart Subject: Re: Transparent proxy using squid, redirect all ssl/https ... ? Date: Mon, 22 May 2006 20:26:34 +0200 Message-ID: <4472025A.1050709@rtij.nl> References: <8963106281166041607@unknownmsgid> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Elijah Alcantara Cc: netfilter@lists.netfilter.org Elijah Alcantara wrote: >> See http://lists.debian.org/debian-user/2004/05/msg01434.html >> >> HTH, >> M4 > > > Checked out the link. Actualy I'm not really planning to cache secure > connections like ssl, I only wanted to be able to redirect that > request to go directly to the internet (bypass squid). > > I currently have an iptable rule for that but it's currently not > working right... Ah, I see. How about -A POSTROUTING -p tcp --dport 443 -j SNAT --to 192.168.100.2 Don't forget to turn on forwarding as well and create appropriate forwarding rules. Personally I would set this firewall between your clients and the Internet, in that case you don't need SNAT tricks, just basic FORWARDING rules. M4