From: "Chris Bennett" Date: Mon, 25 Apr 2005 21:56:26 +0000 Subject: Re: [LARTC] Spill over Message-Id: <001501c549e1$a0b59090$200fa8c0@DELTA> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1876831682==" List-Id: References: In-Reply-To: To: lartc@vger.kernel.org This is a multi-part message in MIME format. --===============1876831682== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01C549B7.B7D130B0" This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C549B7.B7D130B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable A little googling tells me 250 ZAR ~ 42 USD. Is this correct? If so, = ouch.. that's pricey. 3GB (assuming B in this case is BYTE) comes out to about 9kbit / second = over a month, if I did my math correctly. Ouch again. Does the 3GB apply to the total of up and down traffic, or just down? = Because you can't control traffic coming to you very well. You can try = to control TCP traffic with policing, but UDP traffic does its own = thing. Not to mention jokers who decide to flood the link for the hell = of it. Given this new info, it sounds more like you shouldn't try to use the = 512kbit link at all unless the 64kbit link goes down. If you do try to = push "excess" traffic onto it, all that does is encourage the use of = applications that will consume the entire bandwidth available. If that = is really beyond your budget, it doesn't seem like something you'd want = to do. Better to set the expectations at 64kbit so the users don't get = the idea of tuning into Internet radio or something. In fact, if the = 64kbit link does go down, it could be a good idea to police the 512kbit = link down to 64kbit, just so the users don't jump for joy when the = 64kbit link goes down... (keeping in mind that policing is no guarantee = that you'll actually stay below 64kbit usage, especially if a lot of the = traffic is UDP). ----- Original Message -----=20 From: Kenneth Kalmer=20 To: Chris Bennett ; Taylor Grant=20 Cc: lartc=20 Sent: Monday, April 25, 2005 2:48 AM Subject: Re: [LARTC] Spill over Taylor & Chris (and the list) The arguments behind my choice here is cost driven, the 64kbps line is = a fixed monthly rate for unlimited use, the 512kbps line costs us = roughly ZAR250 per 3GB of usage. This can get quite expensive as the = lines in question is for a college and we all know what students do to = bandwidth :) Taken the amount we pay every month for the 64kbps line it's more = economical to over utilize the link as a primary connection than to have = it lying around as a backup. South Africa and data connections don't go = well in the same sentence... As Chris suggested, I need something that can detect when Link A is = saturated and then redirect the traffic over Link B until there is = available bandwidth on Link A again. The rate limit trick of Taylor = might work once I get to understand the usage patterns of these = students. But for at least the first 3 months I won't have proper data = at my disposal. Thanks for your replies! ------=_NextPart_000_0012_01C549B7.B7D130B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
A little googling tells me 250 = ZAR ~=20 42 USD.  Is this correct?  If so, ouch.. that's = pricey.
 
3GB (assuming B in this case is = BYTE) comes=20 out to about 9kbit / second over a month, if I did my math=20 correctly.  Ouch again.
 
Does the 3GB apply to the total = of up and=20 down traffic, or just down?  Because you can't control traffic = coming to=20 you very well.  You can try to control TCP traffic with policing, = but UDP=20 traffic does its own thing.  Not to mention jokers who decide to = flood the=20 link for the hell of it.
 
Given this new info, it sounds = more like=20 you shouldn't try to use the 512kbit link at all unless the 64kbit link = goes=20 down.  If you do try to push "excess" traffic onto it, all = that does=20 is encourage the use of applications that will consume the entire = bandwidth=20 available.  If that is really beyond your budget, it = doesn't seem=20 like something you'd want to do.  Better to set the expectations at = 64kbit=20 so the users don't get the idea of tuning into Internet radio = or=20 something.  In fact, if the 64kbit link does go down, it could be a = good=20 idea to police the 512kbit link down to 64kbit, just so the users = don't=20 jump for joy when the 64kbit link goes down... (keeping in mind that = policing is=20 no guarantee that you'll actually stay below 64kbit usage, especially if = a lot=20 of the traffic is UDP).
----- Original Message -----
From:=20 Kenneth Kalmer
To: Chris Bennett ; Taylor=20 Grant
Cc: lartc
Sent: Monday, April 25, 2005 = 2:48=20 AM
Subject: Re: [LARTC] Spill = over

Taylor &=20 Chris (and the list)

The arguments behind my choice here is = cost=20 driven, the 64kbps line is a fixed monthly rate for unlimited use, the = 512kbps=20 line costs us roughly ZAR250 per 3GB of usage. This can get quite = expensive as=20 the lines in question is for a college and we all know what students = do to=20 bandwidth :)

Taken the amount we pay every month for the 64kbps = line=20 it's more economical to over utilize the link as a primary connection = than to=20 have it lying around as a backup. South Africa and data connections = don't go=20 well in the same sentence...

As Chris suggested, I need = something that=20 can detect when Link A is saturated and then redirect the traffic over = Link B=20 until there is available bandwidth on Link A again. The rate limit = trick of=20 Taylor might work once I get to understand the usage patterns of these = students. But for at least the first 3 months I won't have proper data = at my=20 disposal.

Thanks for your = replies!
------=_NextPart_000_0012_01C549B7.B7D130B0-- --===============1876831682== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============1876831682==--