All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: DNAT routing problem
Date: Thu, 08 May 2008 14:37:40 -0500	[thread overview]
Message-ID: <48235684.6060306@riverviewtech.net> (raw)
In-Reply-To: <3598a5460805081117i7f519321y9ad85f084ba0f484@mail.gmail.com>

On 05/08/08 13:17, Andrea Ranieri wrote:
> Playing a bit with iptables, I observed a strange behavior. For 
> example, if my router is forwarding even a few packets per second 
> (ipv4 only payload), the rule is accepted, but not applied.

<snip>

> Conversely, if no traffic is being forwarded, the rule is accepted 
> and correctly applied.

<snip>

> I really don't understand this behavior, I hope I'm missing something 
> obivious. I'd like to point out that I'm running a standard (debian 
> 2.6.22-14-server) kernel, and each of this two tests, comes from a 
> fresh boot.

(Time to open my mouth and insert my foot.)

NAT rules are applied to the first packet in a connection and then the 
same action is auto-magically applied to all other packets in the 
connection with out passing them through the NAT table.

So what you are seeing is probably very likely based on existing verses 
new connections.

> Thanks in advance, and sorry for the jumbo mail :) Andrea

*nod*



Grant. . . .

  reply	other threads:[~2008-05-08 19:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 18:17 DNAT routing problem Andrea Ranieri
2008-05-08 19:37 ` Grant Taylor [this message]
2008-05-09 10:48 ` Andrea Ranieri
2008-05-09 13:04   ` Cloves Pereira Costa Jr
2008-05-09 13:30   ` Andrea Ranieri
2008-05-09 14:20     ` Grant Taylor
2008-05-09 16:34     ` Andrea Ranieri
2008-05-09 17:55       ` Grant Taylor
2008-05-10  8:56       ` Jan Engelhardt
2008-05-12 16:40         ` Andrea Ranieri
2008-05-10  8:52   ` Jan Engelhardt

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=48235684.6060306@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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 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.