From: Hayden Myers <hayden@spinbox.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: multiple level traffic filtering
Date: Thu, 24 Oct 2002 23:25:31 +0000 [thread overview]
Message-ID: <marc-lartc-103550199207824@msgid-missing> (raw)
I've finally decied that the prio qdisc needs to be attached to root.
Delay should be minimized first, with normal service 2nd, and max
throughput third in the 3 band setup I have planned. Are there any
recommendations? Basically terminals with telnet or ssh should get first
priority with web traffic next and filesharing or transferring third.
Does each band or class under a prio need to point to a seperate qdisc or
can they all point to the same one? With this kind of qdisc, how do I
track a users bandwidth since their traffic will be going through 3
seperate qdiscs based on tos. I'm thinking that I can wrap the prio in an
htb and shape the users traffic before it gets to the prio. This seems
out of whack. I thought that the prio scheduler should always be first in
line so priority traffic gets handled first.
Hayden Myers
Support Manager
Skyline Network Technologies
hayden@spinbox.com
(410)583-1337 option 2
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-10-24 23:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-103550199207824@msgid-missing \
--to=hayden@spinbox.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.