netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Prochazka <billprozac@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Steve Fink <sphink@gmail.com>, netfilter@vger.kernel.org
Subject: Re: NAT table bypass for local traffic
Date: Wed, 28 Apr 2010 16:50:52 -0400	[thread overview]
Message-ID: <h2i812495871004281350j23f2bdefhe18b60101fcf5acc@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1004282136590.18231@obet.zrqbmnf.qr>

Steve,
Thanks for the info.  I have been playing around with it and that
helped...a little.  I played around with the raw table and found that
that fixed the issue of traversing the nat table for related
connections, but it does not fix the initial problem when acks are not
properly dealt with.  A more simple example is that ICMP echo requests
go out the nat table's output chain, but ICMP echo replies do not.

Bill

On Wed, Apr 28, 2010 at 3:46 PM, Jan Engelhardt <jengelh@medozas.de> wrote:
>
> On Wednesday 2010-04-28 19:59, Steve Fink wrote:
>>
> >From the iptables manpage, in the description of the nat table: "This
>>table is consulted when a packet that creates a new connection is
>>encountered."
>>
>>I don't know what mechanism makes related packets in an established
>>connection follow the translation actions set up by the initial
>>packets. There's a magic sheep bit in there somewhere.
>
> A ct entry with mappings already exists when a related packet shows up,
> so there is no need to do a relookup in the table.
>

  reply	other threads:[~2010-04-28 20:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 17:19 NAT table bypass for local traffic Bill Prochazka
2010-04-28 17:59 ` Steve Fink
2010-04-28 19:46   ` Jan Engelhardt
2010-04-28 20:50     ` Bill Prochazka [this message]
2010-04-28 20:55       ` Sven-Haegar Koch
2010-04-29  6:25         ` ratheesh k
     [not found]           ` <001636c5c15232dea504855f65c2@google.com>
2010-04-30  6:25             ` ratheesh k
2010-04-30  7:22             ` ratheesh k
2010-05-01  4:23             ` ratheesh k
2010-05-01 14:29           ` Pascal Hambourg

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=h2i812495871004281350j23f2bdefhe18b60101fcf5acc@mail.gmail.com \
    --to=billprozac@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter@vger.kernel.org \
    --cc=sphink@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).