Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Benny Amorsen <benny+usenet@amorsen.dk>
To: netfilter@vger.kernel.org
Subject: Re: SNAT every packet in a connection
Date: Mon, 28 Jan 2008 09:27:58 +0100	[thread overview]
Message-ID: <m31w82pd69.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: 68252ab80801271847s35873e0fs19480eaf9c31f7fa@mail.gmail.com

"Ashok Rao" <greatarbor@gmail.com> writes:

> From whatever I've read and seen myself, the NAT table is only
> traversed for the first packet of a connection. Hence packets in a
> single connection will always be SNATed to the same IP - Hence the
> packets going out on one of the interfaces will not have the right
> source IP.

The receiving end of the connection will be rather confused when it
gets 10 packets from 1.1.1.1 followed by 10 packets from 2.2.2.2 in
the same connection. Or rather, it should just drop the ones from
2.2.2.2.

What you want is basically impossible.


/Benny



  reply	other threads:[~2008-01-28  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28  2:47 SNAT every packet in a connection Ashok Rao
2008-01-28  8:27 ` Benny Amorsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-28 17:44 Ashok Rao

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=m31w82pd69.fsf@ursa.amorsen.dk \
    --to=benny+usenet@amorsen.dk \
    --cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox