All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TCP Rate Control
Date: Wed, 14 May 2003 18:00:35 +0000	[thread overview]
Message-ID: <marc-lartc-105293531917603@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105291155220508@msgid-missing>

On Wednesday 14 May 2003 13:24, Varun Varma wrote:
> Hi!
>
> Take a setup as follows:
>
> Clients---->[eth0]Proxy/Firewall[eth1]---->Internet
>
> The clients are using the proxy/firewall for various client like
> activities like browsing, email, ftp etc. Most of the traffic is
> "download" traffic, i.e. clients send very small requests and recieve
> very large replies.
>
> I want to do the most common thing...configure download limits/fairness
> of use among the clients.
>
> I understand that I can achieve this by traffic shaping the *outgoing*
> traffic on eth0, but that is a less than optimal solution. The problem
> is that the link to the Internet can still get choked, if too many
> clients start pulling too much data. Traffic shaping on eth0 would limit
> the bandwidth each client sees and TCPs congestion control mechanisms
> *might* indeed slow down the download requests from clients, but this
> does not seem like a elegant way to achieve the result.
Why not?
The only problem you will have is the Proxy.  If you shape on eth0, you shape 
cached objects and objects fetched from the internet.  But you don't want to 
limit traffic that's cached.  So somehow you have to be able to separate 
cached and non cached traffic.

> I am wondering if there is any implementation [or planned project] for
> TCP based rate control, like that provided by commercial solutions like
> PacketShaper and Sitara.
You can do the same (and even more) with a linux box.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-05-14 18:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 11:36 [LARTC] TCP Rate Control Varun Varma
2003-05-14 18:00 ` Stef Coene [this message]
2003-05-14 19:59 ` Brandis Jaroslav
2003-05-14 20:09 ` Stef Coene
2003-05-14 23:06 ` Jose Luis Domingo Lopez
2003-05-15 17:06 ` Stef Coene
2003-05-15 17:53 ` Stef Coene
2003-05-15 17:53 ` Varun Varma
2003-05-15 18:34 ` Varun Varma
2003-05-15 19:15 ` Stef Coene
2003-05-15 19:45 ` Stef Coene
2003-05-15 21:11 ` Varun Varma
2003-05-16  9:20 ` Stef Coene

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-105293531917603@msgid-missing \
    --to=stef.coene@docum.org \
    --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.