From: Nathan Muise <nmuise@node-alpha.homeip.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping with Monthly traffic limits
Date: Wed, 14 Nov 2001 18:48:27 +0000 [thread overview]
Message-ID: <marc-lartc-100576365413062@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100568812618817@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
On Wed, 2001-11-14 at 12:37, Don Cohen wrote:
> I don't see to be ale to post to the list, so a personal response:
>
> I'm currently living in university housing, and they provide an network
> connection. The only limit on transfer speed is link saturation,
> however there are monthly and daily limits for all data transfered to
> and from the internet. Is it currently possible to shape traffic so
> that there is:
> - no limit on local transfers
> - 5G/month, 200/day, 800/night limit on external transfers
> - the ability to still do transfers as fast as the link will allow
> (until it bumps up against transfer limits).
>
> The university does enforce these limits?
> I guess they just stop forwarding when the limits are reached.
> So you don't need to enforce them. You just want to allocate
> them more evenly over time? The easy way would be to limit the
> rate at a finer granularity. Otherwise we get into details of
> the limit - like when do the limited period start/end.
They track, but never stop forwarding; they just start charging at
$0.05/meg ($50/gig). I'd rather avoid that. What I really want to do
is allow uneven allocation, but stay inside the limits. After looking
at the docs, I think I need something like a Token Bucket Filter, but at
large scale: hours and days rather than seconds. The only problem is
that I haven't seen anything that even says if this sort of thing is
possible.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-11-14 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 21:49 [LARTC] Shaping with Monthly traffic limits Nathan Muise
2001-11-14 18:48 ` Nathan Muise [this message]
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-100576365413062@msgid-missing \
--to=nmuise@node-alpha.homeip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox