From: George Alexandru Dragoi <waruiinu@gmail.com>
To: Netfilter Users <netfilter@lists.netfilter.org>
Subject: Re: No PREROUTING for OUTPUT?
Date: Sun, 17 Oct 2004 23:31:23 +0300 [thread overview]
Message-ID: <3063e504101713315f8fb386@mail.gmail.com> (raw)
In-Reply-To: <5FCB4E67C52322BD4ABBF882@10.0.0.4>
The routing decision is done after OUTPUT chains in both nat and
mangle tables, and before POSTROUTING of course. Is this what you
meant?
On Sun, 17 Oct 2004 12:54:11 -0700, Kenneth Porter
<shiva@sewingwitch.com> wrote:
> Can anyone confirm that the PREROUTING chain is absent from the OUTPUT
> packet path? I wanted to tag my UDP packets with TOS Minimize-Delay so that
> they'd go in my high-priority traffic shaping queues, but if PREROUTING
> isn't used in the output path, the packets can't be tagged until after
> they've been through the shaper. (Isn't the shaper part of "routing
> decision" in the diagrams?)
>
>
--
Bla bla
next parent reply other threads:[~2004-10-17 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5FCB4E67C52322BD4ABBF882@10.0.0.4>
2004-10-17 20:31 ` George Alexandru Dragoi [this message]
2004-10-17 21:10 ` No PREROUTING for OUTPUT? Kenneth Porter
[not found] ` <06B6B683FC4088203BA6B8D7@10.0.0.4>
2004-10-18 11:11 ` George Alexandru Dragoi
2004-10-17 19:54 Kenneth Porter
2004-10-18 14:51 ` Aleksandar Milivojevic
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=3063e504101713315f8fb386@mail.gmail.com \
--to=waruiinu@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox