From: "Jay Wineinger" <shad@wnoc.com>
To: lartc@vger.kernel.org
Subject: [LARTC] questions
Date: Mon, 08 Sep 2003 18:14:04 +0000 [thread overview]
Message-ID: <marc-lartc-106304483118069@msgid-missing> (raw)
Hey guys,
Im going to be setting up a qos system for the college I attend and I
had some questions. First, the box will be a transparent bridge and I would
like to prioritize traffic (3 class/types only, [interactive, web+mail+etc,
bulk]) and also limit single ips to specified up/down speeds. I want to use
HTB.
1) the network here will have about 500-600 computers on the network,
with 400 active at any one time. Any ideas on what kind of hardware will be
needed to accomodate this? They have given me a P-II 350 with 256Mb of RAM
and 2 realtek based 10/100 NICs. Should this be enough?
2) What would be the most efficient way (qdisc/class structure) to
accomplish this? The school's main link is approx 6mbit, yet if I split
that among the anticipated active computers, that would average about 15kbit
per computer, which is terrible. So, that means if I want to allot any
useful amount of bandwidth to all of the computers, my total alloted
bandwidth would be greater than the link. Am I correct in my reasoning
here? If so, what would all of you experienced shapers recommend for my
setup? (tree diagrams, descriptions would be great)
3) iptables marking will not work over the bridge (correct?) so I need
to learn to use u32 filter classifiers. Are there any in depth howto's, etc
out there? Im looking at the LARTC page on it and Im still pretty confused.
4) Anything else I should remember/consider?
Please CC replies to my address shad at wnoc dot com
Jay
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-09-08 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 18:14 Jay Wineinger [this message]
2003-09-09 15:24 ` [LARTC] questions 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-106304483118069@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 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.