All of lore.kernel.org
 help / color / mirror / Atom feed
From: GMail Isaac Gonzalez <isaak.gonzalez@gmail.com>
To: Giles Coochey <giles@coochey.net>
Cc: "Gáspár Lajos" <swifty@freemail.hu>,
	"netfilter list" <netfilter@vger.kernel.org>
Subject: Re: POSTROUTING SNAT only reply packets
Date: Mon, 17 Jan 2011 12:07:43 +0100	[thread overview]
Message-ID: <4D3422FF.8090803@gmail.com> (raw)
In-Reply-To: <4D34200F.5050307@coochey.net>

Ok,

Thanks for the replies, I was doing some tests to asure the connection 
issues. It's compulsory that the load balancer receive the return packets.


El 17/01/11 11:55, Giles Coochey escribió:
> On 17/01/2011 11:38, Gáspár Lajos wrote:
>> Hi,
>>
>> 2011-01-17 11:16 keltezéssel, GMail Isaac Gonzalez írta:
>>> Hi,
>>>
>>
>>> I've doing some testing and seems that iptables only do SNAT on NEW 
>>> connections, and I need to change the ip address of replied packets. 
>>> Anybody know some workaround? If anobody do not know some workaround 
>>> can you confirm that it's not posible to do this with iptables?
>>
>> read again the NAT part in the manual:
>> man iptables
>>
>> nat table:
>>               nat:
>>                   This table is consulted when a packet that creates 
>> a new connection is encountered.  It consists of three built-ins: 
>> PREROUTING (for altering packets as soon as they come in), OUTPUT 
>> (for  altering  locally-gener-
>>                   ated packets before routing), and POSTROUTING (for 
>> altering packets as they are about to go out).
>>
>> DNAT target:
>>
>>    DNAT
>>        This  target  is  only valid in the nat table, in the 
>> PREROUTING and OUTPUT chains, and user-defined chains which are only 
>> called from those chains.  It specifies that the destination address 
>> of the packet should be modified
>>        (and all future packets in this connection will also be 
>> mangled), and rules should cease being examined.  It takes one type 
>> of option:
>>
>> SNAT target:
>>
>>    SNAT
>>        This target is only valid in the nat table, in the POSTROUTING 
>> chain.  It specifies that the source address of the packet should be 
>> modified (and all future packets in this connection will also be 
>> mangled), and rules  should
>>        cease being examined.  It takes one type of option:
>>
>>
>>> I've tried the next ip tables rules and only work when I do NEW 
>>> connections from the web server.
>>>
>>> -A POSTROUTING -o br0 -s WE_SERVER_ADDR -p tcp -m tcp --sport 80 
>>> --dport 1024:65535 -j SNAT --to-source LOAD_BALANCER_ADDR
>>>
>>> Thanks in advance.
>>>
>>> Isaac González
>>>
>>
>> You should do all of the NAT-ing ON THE LOAD BALANCER:
>>
>
> I have to agree - if you are doing NAT you want to avoid any type of 
> asymmetric routing - especially you NEED to make sure that the device 
> that is doing the NAT (be it for load balancing or other reasons) 
> receives the return packets. You cannot keep a TCP connection going if 
> there is not some sort of state information being shared between the 
> devices otherwise.
>


  reply	other threads:[~2011-01-17 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 10:16 POSTROUTING SNAT only reply packets GMail Isaac Gonzalez
2011-01-17 10:38 ` Gáspár Lajos
2011-01-17 10:51   ` GMail Isaac Gonzalez
2011-01-17 11:14     ` Amos Jeffries
2011-01-17 10:55   ` Giles Coochey
2011-01-17 11:07     ` GMail Isaac Gonzalez [this message]
2011-01-17 11:36     ` Jan Engelhardt
2011-01-17 11:41       ` Giles Coochey
2011-01-17 11:57         ` GMail Isaac Gonzalez
2011-01-17 12:10           ` Jan Engelhardt
2011-01-17 23:07 ` Michael Vallaly
  -- strict thread matches above, loose matches on Subject: below --
2011-01-17 10:15 Isaac González

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=4D3422FF.8090803@gmail.com \
    --to=isaak.gonzalez@gmail.com \
    --cc=giles@coochey.net \
    --cc=netfilter@vger.kernel.org \
    --cc=swifty@freemail.hu \
    /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.