[LARTC] Shaping with Monthly traffic limits

[LARTC] Shaping with Monthly traffic limits

[Nathan Muise]

[-- Attachment #1: Type: text/plain, Size: 770 bytes --]

I've taken a look at the list archives, the Advanced Routing HOWTO, and
done a quick netsearch, but still don't know how to solve my problem.  

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).

Any help would be appreciated... a thread I might have missed, a
webpage, anything.

Thanks in advance, 
Nathan

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [LARTC] Shaping with Monthly traffic limits

[Nathan Muise]

[-- 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 --]