From: Thomas Bushnell BSG <tb@becket.net>
To: lartc@vger.kernel.org
Subject: [LARTC] elementary usage clamping
Date: Wed, 06 Jun 2007 04:37:08 +0000 [thread overview]
Message-ID: <1181104629.22239.25.camel@localhost> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1185 bytes --]
I'm pretty smart, and was once regarded as pretty network and computer
savvy. But the world has obviously passed me by!
I have a server in a colocation facility, and I was recently hit by a
bill for overage; I used more bandwidth than I expected, and I must
pay.
So now, I want to bother with packet shaping on the server. The *most*
important thing is to clamp bandwidth to the 1Mbps that my contract
allows for. This is well within my ordinary usage; there is no reason
for me to want more. But I must be careful about overage: when I am
transferring large amounts of data, I don't mind waiting for how long it
takes at 1Mbps (minus overhead), but I certainly don't want to pay lots
extra!
This is the most important thing. The next thing is that, once the
bandwidth has been clamped, I want to have the ability to be flexible
about shaping traffic. Obviously such things as ssh need priority, and
then AFS, and then ftp and http. But this is still really only a
single-user case, so even if the shaping is not so great, it's ok.
I cannot, for the life of me, figure out what tcng syntax would get me
what I want. Can someone help me?
Thomas
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2007-06-06 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 4:37 Thomas Bushnell BSG [this message]
2007-06-06 15:42 ` [LARTC] elementary usage clamping Marco Aurelio
2007-06-06 19:28 ` Thomas Bushnell BSG
2007-06-06 20:58 ` Marco Aurelio
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=1181104629.22239.25.camel@localhost \
--to=tb@becket.net \
--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.