From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Fair bandwidth sharing
Date: Sun, 21 Nov 2004 17:13:29 +0000 [thread overview]
Message-ID: <41A0CCB9.21B4C70F@iswest.com> (raw)
In-Reply-To: <30d13862041121033627fc41f2@mail.gmail.com>
Craig Main wrote:
>
> Hi all,
>
> I have been playing with tc trying to share the available bandwidth
> fairly between all the terminals in my internet cafe.
>
> I spend a while and had some help and setup some htb classes on my
> outgoing interface, I has now dawned on me that this will only shape
> the outgoing traffic, and if someone starts a large download, all the
> available incomming bandwidth will be used by the one terminal.
>
> Will the right thing to do be to setup tc classes/queues on my LAN
> interface to limit the bandwidth, or must I setup a imq interface and
> classify on that device?
google lartc rio martin cafe
and read the first item.
You do need to shape downloads, but how you go about that does not
necessarily involve IMQ. Although I'm not dealing with a cafe, I have a
machine that has 2 interfaces:
inet <-> eth1 <-> shaper <-> eth0 <-> LAN switch
I shape on both eth1 and eth0, shaping downloads initiated in the LAN on
eth0. I have not yet, but may if necessary, police. The police would
attempt to prevent any one internal user from hogging all the download
bandwidth by dropping packets based on the internal IP and the quantity
of data per IP.
gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-11-21 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 11:36 [LARTC] Fair bandwidth sharing Craig Main
2004-11-21 17:13 ` gypsy [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=41A0CCB9.21B4C70F@iswest.com \
--to=gypsy@iswest.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.