From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bas Verhoeven Subject: Re: iptables NAT routing issues Date: Thu, 10 May 2007 16:21:56 +0200 Message-ID: <46432A84.2010409@bserved.nl> References: <4640E893.1010206@bserved.nl> <4640FAD0.9050301@plouf.fr.eu.org> <4640FDA9.5000706@bserved.nl> <464101DA.4070102@plouf.fr.eu.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <464101DA.4070102@plouf.fr.eu.org> 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: Pascal Hambourg Cc: netfilter@lists.netfilter.org Pascal Hambourg wrote: > Use the outer box as a gateway, if it is in the same network. You do > not have to use it as the default gateway for all traffic but at least > for the HTTP return traffic. This could be done with iptables and > advanced routing on the web server, for instance using the source port > 80 to MARK packets or using CONNMARK/connmark. I wasn't aware of that option, it seems to work fine ;-) Thanks. > > You could try to use the NOTRACK target on the web server in order to > prevent the incoming SYN packets from creating a new connection, so > the replies could be SNATed. But I would not bet a euro-cent on such a > dirty method. If someone asks who suggested it, don't say it's me. ;-) >