From: "Jay Wineinger" <shad@wnoc.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] marking
Date: Tue, 28 Jan 2003 21:47:44 +0000 [thread overview]
Message-ID: <marc-lartc-104379087632316@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101665894626463@msgid-missing>
Ok, that KPTD helps a bit. Question about that though, it seems that a
forwarded packet will have 3 chances at getting marked (PRE,FORWARD,POST);
is that correct? Similarly, a packet originating on the QoS box will have 2
mark chances (OUTPUT and POST). If thats correct, is there any advantage
to using one or the other. I dont see why you wouldnt just do everything in
POSTROUTING since all packets go there eventually according to the diagram.
btw, thanks for all the help
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-28 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 21:14 [LARTC] Marking Ali badilli
2002-03-21 21:06 ` Viktor Kemmet
2003-01-27 4:50 ` [LARTC] marking Jay Wineinger
2003-01-27 18:17 ` Stef Coene
2003-01-28 3:55 ` Jay Wineinger
2003-01-28 9:52 ` Stef Coene
2003-01-28 19:56 ` Stef Coene
2003-01-28 21:47 ` Jay Wineinger [this message]
2003-01-29 17:33 ` Stef Coene
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-104379087632316@msgid-missing \
--to=shad@wnoc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox