All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Verhoeven <netfilter@bserved.nl>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: iptables NAT routing issues
Date: Thu, 10 May 2007 16:21:56 +0200	[thread overview]
Message-ID: <46432A84.2010409@bserved.nl> (raw)
In-Reply-To: <464101DA.4070102@plouf.fr.eu.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. ;-)
>



  reply	other threads:[~2007-05-10 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 21:16 iptables NAT routing issues Bas Verhoeven
2007-05-08 22:25 ` Jan Engelhardt
2007-05-08 22:33   ` Pascal Hambourg
2007-05-08 22:37     ` Jan Engelhardt
2007-05-08 22:46       ` Bas Verhoeven
2007-05-08 22:48         ` Maximilian Wilhelm
2007-05-08 23:03         ` Pascal Hambourg
2007-05-10 14:21           ` Bas Verhoeven [this message]
2007-05-10 19:31             ` Pascal Hambourg
2007-05-10 20:06               ` Bas Verhoeven
2007-05-10 22:14                 ` Pascal Hambourg
2007-05-08 22:37 ` Maximilian Wilhelm

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=46432A84.2010409@bserved.nl \
    --to=netfilter@bserved.nl \
    --cc=netfilter@lists.netfilter.org \
    --cc=pascal.mail@plouf.fr.eu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.