From: Adam Schrader <schrader2k2@yahoo.com>
To: lartc@vger.kernel.org
Subject: [LARTC] how to guarantee bandwidth for a service
Date: Thu, 10 Apr 2003 07:32:59 +0000 [thread overview]
Message-ID: <marc-lartc-104996008421432@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
How can I guarantee a certain amount of bandwidth for a certain service, ie web browsing (port 80) or half-life (27015) or even per ip and then just leave the rest of the bw to be fought over. The problem is that people have file sharing programs edonkey, kazaa and so on and rather than keep track of them all and try to manage their bandwidth usage so as so leave some for the other services I would just like to let them fight over as much bw as they can take after guaranteeing a certain amount for certain services/ips.
-Adam
---------------------------------
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
[-- Attachment #2: Type: text/html, Size: 722 bytes --]
next reply other threads:[~2003-04-10 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 7:32 Adam Schrader [this message]
2003-04-10 16:20 ` [LARTC] how to guarantee bandwidth for a service Jay Wineinger
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-104996008421432@msgid-missing \
--to=schrader2k2@yahoo.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.