From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Limit bandwidth per client
Date: Tue, 13 May 2003 17:11:52 +0000 [thread overview]
Message-ID: <marc-lartc-105284721529467@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105275594907949@msgid-missing>
On Tuesday 13 May 2003 16:32, David Reoch wrote:
> That is the best, detailed, straight-forward howto on tc I've ever seen!
> (There are probablly others out there, and no offense to authors of any
> that I just haven't seen). Thanks!
>
> I have been off and on trying to get my squid transparent proxy/cache
> server to do tc for me, but it just doesn't seem to work, and I wonder
> if you can offer any advice.
The problem is that squid is a local running app. And tc does not know if
sqiud is using it's cache to server the objects. Ideally, you should be able
to mark the packets within squid like you can with iptables.
> My network looks just like you've described below, except that your
> 'router1' is my 'transparent cache', running as a bridge, where eth0 and
> eth1 are bridge interfaces (br0).
>
> I am beginning to draw the conclusion that I cannot do tc with a bridge,
> and that I must route. Do you have any suggestions?
Shaping on a bridge is possible. If you use the u32 filter, you can get in
some trouble that can be solve with a kernel patch :
http://www.docum.org/stef.coene/qos/faq/cache/41.html
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/
prev parent reply other threads:[~2003-05-13 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 16:08 [LARTC] Limit bandwidth per client Stuart Mackintosh
2003-05-12 16:39 ` james jones
2003-05-13 14:32 ` David Reoch
2003-05-13 17:11 ` Stef Coene [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=marc-lartc-105284721529467@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.