From: "Daniel K." <daniel@yaTack.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute + mark question
Date: Tue, 14 May 2002 15:55:29 +0000 [thread overview]
Message-ID: <marc-lartc-102139186120409@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102138771915888@msgid-missing>
Ciprian Niculescu wrote:
> i did this i asked, this is what it is at sectio 6, in the link you
> provided
>
> Incoming / \ Outgoing
> -->[Routing ]--->|FORWARD|------->
> [Decision] \_____/ ^
> | |
> v ____
> ___ / \
> / \ |OUTPUT|
> |INPUT| \____/
> \___/ ^
> | |
> ----> Local Process ----
>
> in this the local it's never "routing decision" but let's say it's for
> simplicity :))
>
> and your's is wrong too, Local Proces -> OUTPUT -> POSTROUTING -> Out
>
> - so the routing decision is where?
The routing desicion is between OUTPUT an POSTROUTING,
POSTROUTING means AFTER routing.
So you may say: "Locally generated packet" -> OUTPUT -> "Routing
Desicion" -> POSTROUTING.
If you want to Mangle(e.g mark) Locally generated packets, you have to
do so in the OUTPUT table. In this case it will be marked for the
routing descicion which comes next.
Daniel K.
> - and i tryed to put the match in POSTROUTING and did not match
>
> C
>
>
> Daniel K. wrote:
>
>> Ciprian Niculescu wrote:
>>
>>> does anybody have the hole packet path, a grafic, with: mangle, nat,
>>> filter, routing, tc, tunel, for local generated pachetd and for
>>> FORWARDed pachets???
>>
>>
>>
>> This is how IPTables look like.
>>
>> /----------\ /-------\ /-----------\
>> IN--->---< PREROUTING >--->---< FORWARD >--->---< POSTROUTING >--->--OUT
>> \----------/ \-------/ \-----------/
>> \ /
>> \ /
>> /-----\ /-------------\ /------\
>> < INPUT >--->---< LOCAL PROCESS >--->---< OUTPUT >
>> \-----/ \-------------/ \------/
>>
>>
>> Maybe you should read some of Rusty's Remarkably Unreliable Guides
>> http://netfilter.samba.org/unreliable-guides/
>>
>> In particular, section 6 of Linux 2.4 Packet Filtering HOWTO
>> http://netfilter.samba.org/unreliable-guides/packet-filtering-HOWTO/packet-filtering-HOWTO.linuxdoc.html
>>
>>
>>
>> Daniel K.
>>
>> _______________________________________________
>> LARTC mailing list / LARTC@mailman.ds9a.nl
>> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-05-14 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 14:47 [LARTC] iproute + mark question Ciprian Niculescu
2002-05-14 15:20 ` Daniel K.
2002-05-14 15:36 ` Ciprian Niculescu
2002-05-14 15:55 ` Daniel K. [this message]
2002-05-14 16:13 ` Ciprian Niculescu
2002-05-14 16:21 ` Julian Anastasov
2002-05-15 16:14 ` Jason A. Pattie
2002-05-15 16:27 ` Ciprian Niculescu
2002-05-15 16:47 ` Jason A. Pattie
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=marc-lartc-102139186120409@msgid-missing \
--to=daniel@yatack.com \
--cc=lartc@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.