From: Leonardo Balliache <leoball@opalsoft.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] OUTPUT chain marking after or before routing?
Date: Sun, 20 Jul 2003 15:19:54 +0000 [thread overview]
Message-ID: <marc-lartc-105871450026971@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105842045025983@msgid-missing>
Hi,
At 08:04 a.m. 18/07/03 +0300, you wrote:
>----- Original Message -----
>From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
>To: "Chijioke Kalu" <kchijioke@msn.com>
>Cc: <catalin@electricant.ambra.ro>; <lartc@mailman.ds9a.nl>
>Sent: Thursday, July 17, 2003 6:55 PM
>Subject: Re: [LARTC] OUTPUT chain marking after or before routing?
>
>
> > Catalin,
> >
> > >When I try to connect to a smtp port somewhere in the Internet, tcpdump
>show
> > >me that these packets go to the eth2 interface (the main table default
> > >route). I don't know where is my mistake but it seems that the marking in
> > >the OUTPUT chain occurs AFTER and not BEFORE routing. Is this a correct
> > >behaviour? How can I solve my problem? Please help!
> >
> > According to my reading of the KPTD (and my understanding), packets
> > generated on the local machine have already been routed by the time the
> > OUTPUT chain is traversed. See:
> >
> > http://www.docum.org/stef.coene/qos/kptd/
> >
>
>I'm very confused now. Look what is written in the iptables man page:
>
>#############
> mangle This table is used for specialized packet alteration. It has two
>built-in
> chains: PREROUTING (for altering incoming packets before
>routing) and OUTPUT
> (for altering locally-generated packets before routing).
>######################
>
>So how it is? OUTPUT marks packets AFTER or BEFORE routing?
Just before "output routing". OUTPUT is for locally generated packets.
These packets are also to be routed (output routing). OUTPUT mangle marks
"locally generated" packets just before they are "output routing".
Perhaps confussion is because also input routing exists where a decision is
taken: is this packet for this host or it has just to be forwarded? Read
Stef´s remarks on the diagram:
Output routing : the local process selects a source address and a route.
This route is attached to the packet and used later.
Best regards,
Leonardo Balliache
Practical QoS
http://opalsoft.net/qos
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-07-20 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 5:37 [LARTC] OUTPUT chain marking after or before routing? Catalin Borcea
2003-07-17 6:04 ` ???????? ?????
2003-07-17 6:31 ` Catalin Borcea
2003-07-17 6:37 ` ???????? ?????
2003-07-17 7:15 ` Catalin Borcea
2003-07-17 7:32 ` ???????? ?????
2003-07-17 14:08 ` Chijioke Kalu
2003-07-17 15:55 ` Martin A. Brown
2003-07-17 16:50 ` lartc
2003-07-18 5:04 ` Catalin Borcea
2003-07-18 18:41 ` Martin A. Brown
2003-07-18 18:46 ` Martin A. Brown
2003-07-19 7:45 ` lartc
2003-07-20 15:19 ` Leonardo Balliache [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=marc-lartc-105871450026971@msgid-missing \
--to=leoball@opalsoft.net \
--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.