From: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>
To: netfilter@lists.netfilter.org, netfilter-devel@lists.netfilter.org
Subject: Re: Bug/Problem with DNAT on OUTPUT chain (-t nat -A OUTPUT) that breaks routing? (fwd)
Date: Thu, 23 Oct 2003 13:29:09 -0400 [thread overview]
Message-ID: <3F980FE5.1000108@Loudoun-Fairfax.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0310231127470.29188-100000@kinison.puremagic.com>
Evan Harris wrote:
>Ok, I've upgraded to kernel 2.4.22, and the same behaviour is being
>exhibited.
>
>To recap the problem:
>
>Packets being nat'd on the OUTPUT chain of a machine are still being sent on
>the same interface they would have without the nat, and ignoring the route
>that aims them to the right iface for that dest addr.
>
>Evan
>
>
>
I haven't seen the rest of this thread, so I may have missed something,
but why are you doing DNAT on the nat OUTPUT chain? DNAT is usually done
on the nat PREROUTING chain and SNAT on the POSTROUTING chain. Anything
done in filter OUTPUT, mangle POSTROUTING, or nat POSTROUTING could
change the direction of your packets before they leave your host.
Jeff
next prev parent reply other threads:[~2003-10-23 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 0:58 Bug/Problem with DNAT on OUTPUT chain (-t nat -A OUTPUT) that breaks routing? (fwd) Evan Harris
2003-10-23 2:37 ` Patrick McHardy
2003-10-23 16:30 ` Evan Harris
2003-10-23 16:30 ` Evan Harris
2003-10-23 17:16 ` Patrick McHardy
2003-10-23 18:25 ` Evan Harris
2003-10-23 18:25 ` Evan Harris
2003-10-23 17:29 ` Jeffrey Laramie [this message]
2003-10-28 13:44 ` Evan Harris
2003-10-28 13:44 ` Evan Harris
2003-10-23 17:09 ` Henrik Nordstrom
2003-10-23 17:09 ` Henrik Nordstrom
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=3F980FE5.1000108@Loudoun-Fairfax.com \
--to=jalaramie@loudoun-fairfax.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@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.