From: Michael Gundlach <gundlach@cs.uga.edu>
To: netfilter-devel@lists.netfilter.org
Subject: Re: PREROUTING doesn't catch all packets?
Date: Wed, 19 Feb 2003 17:50:49 -0500 [thread overview]
Message-ID: <20030219175049.B8641@cs.uga.edu> (raw)
In-Reply-To: <20030219201931.GA16304@oknodo.bof.de>; from bof@bof.de on Wed, Feb 19, 2003 at 09:19:31PM +0100
Yep, that did the trick. thanks a lot.
michael
On Wed Feb 19, 2003 at 09:19PM, Patrick Schaaf wrote:
> > iptables -t nat
>
> The NAT table NEVER sees any packet belonging to already existing
> conntrack entries. The sole purpose of the NAT table is to select
> NAT actions for NEW conntrack entries.
>
> Thus, the behaviour you see, is the desired mode of operation,
> regardless of bridging. It is the way the NAT table is intended
> to operate.
>
> > I need to use PREROUTING for an application that is modifying
> the destination IP of incoming packets, so "use the FORWARDING chain
> instead" isn't a sufficient answer.
>
> The answer may be "use the PREROUTING chain of the '-t mangle' table".
>
> best regards
> Patrick
prev parent reply other threads:[~2003-02-19 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 19:18 PREROUTING doesn't catch all packets? Michael Gundlach
2003-02-19 20:19 ` Patrick Schaaf
2003-02-19 22:50 ` Michael Gundlach [this message]
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=20030219175049.B8641@cs.uga.edu \
--to=gundlach@cs.uga.edu \
--cc=netfilter-devel@lists.netfilter.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.