From: Evgeni Gechev <etg@setcom.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb: HowTo identify squid cache hits
Date: Thu, 26 May 2005 14:04:57 +0000 [thread overview]
Message-ID: <4295D789.4080109@setcom.bg> (raw)
In-Reply-To: <20050526133242.GA11315@sysop-2.atlascollege.nl>
Peter Kaagman wrote:
>Hi list...
>
>I work for a school in the netherlands with a 2mbit Internet uplink and
>about 3800 eager student who want to play games on the Internet using
>one of our 800 workstations.
>
>Problem was that those game playing students are concentrated in 2 of
>our 6 physical locations... and they consumed the bandwidth which the
>other location would like to use for educational purposes.
>
>The thing we did first was use squid... with success. The hit ratio on
>data transfer is 25-30%... "free" bandwidth.
>
>Today I took the plunge and started to use HTB traffic shaping... and
>(to my surprise) I got it going without much troubles.
>
>The setup I have chosen first divides the load over two classes:
>- one for Internet rate 2mbit and a 2mbit ceil
>- a second for our DMZ rate 98mbit and a 100mbit ceil
>
>Next I sub-classed the Internet bucket into 6 classes each with a
>333kbit rate and a 2mbit ceil.
>
>This has had the effect that my DMZ can be accessed at full speed while
>they fairly share the Internet uplink.
>
>And the way it looks now it works :D
>Hail to all those people who wrote those fine docs _o_
>
>This is enough reason to address this list... just to say "Thank you!",
>but there is more.
>
>At the moment I do not max out my Internet link... reason for this is I
>guess the squid proxy...
>The way it works now is that I have 2 types of filters in effect:
>- The DMZ: all packages with a src ip from my DMZ go to the big 98/100
> bucket.
>- The Internet: all packages with a dst ip in one of our 6 networks
> gets placed in one of the 6 333/2000 buckets.
>
>But there is of course a src of packages I do not catch this way... and
>these are the squid cache hits. Because I filter on destination the cache
>hits get treated the same as cache misses. But cache hits are in effect
>local traffic... they do not originate from the Internet.
>
>So here (finally) the question..
>Is there a way to identify cache hits from misses?
>
>I took a look at the advanced filtering chapter of course, but am
>really dazzled by that (and I thought I understood TCP/IP a bit ;)).
>
>Some further info that would perhaps help is that squid is run as a
>transparant proxy on the router/firewall.
>
>regards
>
>Peter Kaagman
>
>
http://www.it-academy.bg/zph/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-05-26 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 13:32 [LARTC] htb: HowTo identify squid cache hits Peter Kaagman
2005-05-26 13:49 ` Justin Schoeman
2005-05-26 14:00 ` Marcin Kałuża
2005-05-26 14:04 ` Evgeni Gechev [this message]
2005-05-26 14:05 ` Daniel Lupescu
2005-05-26 14:33 ` Peter Surda
2005-05-26 17:49 ` Pan'ko Alexander
2005-05-26 18:56 ` Andy Furniss
2005-05-26 19:13 ` Pan'ko Alexander
2005-05-26 19:41 ` Andy Furniss
2005-05-26 19:47 ` Peter Kaagman
2005-05-26 19:59 ` Peter Kaagman
2005-05-27 0:09 ` Lewis Shobbrook
2005-05-27 9:13 ` Konrad
2005-05-30 15:01 ` Andy Furniss
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=4295D789.4080109@setcom.bg \
--to=etg@setcom.bg \
--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.