Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Giles Coochey <giles@coochey.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: "Gáspár Lajos" <swifty@freemail.hu>,
	"GMail Isaac Gonzalez" <isaak.gonzalez@gmail.com>,
	"netfilter list" <netfilter@vger.kernel.org>
Subject: Re: POSTROUTING SNAT only reply packets
Date: Mon, 17 Jan 2011 12:41:40 +0100	[thread overview]
Message-ID: <4D342AF4.6070504@coochey.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1101171231200.29904@obet.zrqbmnf.qr>

[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

On 17/01/2011 12:36, Jan Engelhardt wrote:
> On Monday 2011-01-17 11:55, Giles Coochey wrote:
>>> 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.
> Not strictly. You could utilize a second device whose CTs are synchronized
> with the LB to apply the reverse transform, using conntrackd.
> Sort of like
>
> digraph { internet ->  lb; lb ->  web; web ->  unnat; unnat ->  internet; };
>
> but it only looks feasible to me if your LB is already computationally
> crowded.
> --
It also requires the loadbalancer to be using netfilter as well.

If it's a hardware load balancer with proprietary methods then you will 
need symmetric routing through it, unless it supports some form of TCP 
state sharing.

-- 
Best Regards,

Giles Coochey
NetSecSpec Ltd
NL T-Systems Mobile: +31 681 265 086
NL Mobile: +31 626 508 131
Gib Mobile: +350 5401 6693
Email/MSN/Live Messenger: giles@coochey.net
Skype: gilescoochey




[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5137 bytes --]

  reply	other threads:[~2011-01-17 11:41 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
2011-01-17 11:36     ` Jan Engelhardt
2011-01-17 11:41       ` Giles Coochey [this message]
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=4D342AF4.6070504@coochey.net \
    --to=giles@coochey.net \
    --cc=isaak.gonzalez@gmail.com \
    --cc=jengelh@medozas.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox