From: Alexander Samad <alex@samad.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Classful Queuing
Date: Tue, 12 Oct 2004 03:04:03 +0000 [thread overview]
Message-ID: <20041012030403.GS522@samad.com.au> (raw)
In-Reply-To: <20041012010156.GY16095@cerberus>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
On Mon, Oct 11, 2004 at 07:31:28PM -0600, Jamin W. Collins wrote:
> On Tue, Oct 12, 2004 at 11:16:54AM +1000, Alexander Samad wrote:
> >
> > I think what you need to look for is marking of packets with netfilter -
> > let it classify and then used tc to place the properly marked packets
> > into the proper queue
> >
> > Because you can mark in the PREROUTING table in mangle before it is enc
>
> But will the mark still exist after the encryption/encapsulation? Plus,
> that only deals without outgoing not incoming utilization if I'm
> following this correctly. The incoming packets would not be
> identifiable until they were taken off the eth1 interface for their
> specific interface (ppp or ipsec), right?
not so about ingres, but the marking stay with the packet after the enc
( well on 2.6 with native stack it does). I use this for marking
packets.
>
> --
> Jamin W. Collins
>
> "Never underestimate the power of very stupid people in large groups."
> -- John Kenneth Galbraith
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-12 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 1:01 [LARTC] Classful Queuing Jamin W. Collins
2004-10-12 1:16 ` Alexander Samad
2004-10-12 1:31 ` Jamin W. Collins
2004-10-12 3:04 ` Alexander Samad [this message]
2004-10-12 3:46 ` rsenykoff
2004-10-12 6:25 ` Robert Felber
2004-10-12 7:05 ` Alexander Samad
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=20041012030403.GS522@samad.com.au \
--to=alex@samad.com.au \
--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.