All of lore.kernel.org
 help / color / mirror / Atom feed
From: Craig Main <satuxman@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Fwd: Alternatives to Squid
Date: Sun, 12 Dec 2004 08:13:12 +0000	[thread overview]
Message-ID: <30d1386204121200134b380498@mail.gmail.com> (raw)

---------- Forwarded message ----------
From: Craig Main <satuxman@gmail.com>
Date: Sat, 11 Dec 2004 16:57:00 +0200
Subject: Alternatives to Squid
To: Gentoo User <gentoo-user@lists.gentoo.org>


Hi all,

I have an internet cafe connected on a not so fast leased line (64k).

I definately need to use a caching proxy. I currently use squid, and
it works fine. However if one of the terminals has a 'power surfer',
they tend to use all of the bandwidth leaving not much for the other
terminals.

I have tryed squids delay pools, but they don't really do what I want.
What I really need is to split all the bandwidth between the terminals
that are drawing traffic fairly.

I have setup tc qdiscs and classes on the interface between the proxy
and the terminals sharing the bandwith fairly and using sfq qdiscs for
when the limit is reached. The problem with this scenario is that
squid still pulls the info from the net unfairly, so only traffic from
squid to the terminals is managed.

I was hoping that there might be an alternative to squid that handles
bandwidth management better.

Can anyone recommend one, or can someone let me know of a better way
of managing the bandwidth?

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

             reply	other threads:[~2004-12-12  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-12  8:13 Craig Main [this message]
2004-12-20  3:54 ` [LARTC] Fwd: Alternatives to Squid Ow Mun Heng

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=30d1386204121200134b380498@mail.gmail.com \
    --to=satuxman@gmail.com \
    --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.