All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Verhoeven <netfilter@bserved.nl>
To: netfilter@lists.netfilter.org
Subject: Re: iptables NAT routing issues
Date: Wed, 09 May 2007 00:46:01 +0200	[thread overview]
Message-ID: <4640FDA9.5000706@bserved.nl> (raw)
In-Reply-To: <Pine.LNX.4.61.0705090036060.2342@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
>
>> Assuming that the outbound server is the default gateway for the web server and
>> receives the return traffic, of course.
>>     
>
> You'd be kinda screwed if that was not the case. Because the 'nat' table
> is only consulted for NEW connections afaics, the reply packets do _not_
> get SNATed, since the _first_ packet was the TCP SYN, which makes the
> connection ESTABLISHED when input processing is done.
>
>   
The webserver has its own gateway, and that's not the outer box. You 
seem to be describing the exact problem i'm seeing in tcpdump; new 
connections get snat'ed, 'forwarded' connections do not.

Is there really no solution for this?

Bas


  reply	other threads:[~2007-05-08 22:46 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 [this message]
2007-05-08 22:48         ` Maximilian Wilhelm
2007-05-08 23:03         ` Pascal Hambourg
2007-05-10 14:21           ` Bas Verhoeven
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=4640FDA9.5000706@bserved.nl \
    --to=netfilter@bserved.nl \
    --cc=netfilter@lists.netfilter.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.