From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb: HowTo identify squid cache hits
Date: Thu, 26 May 2005 19:41:32 +0000 [thread overview]
Message-ID: <4296266C.3050902@dsl.pipex.com> (raw)
In-Reply-To: <20050526133242.GA11315@sysop-2.atlascollege.nl>
Pan'ko Alexander wrote:
> On Thu, 26 May 2005 19:56:09 +0100
> Andy Furniss <andy.furniss@dsl.pipex.com> wrote:
>
>
>>Peter Kaagman wrote:
>>
>>
>>>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.
>>
>>If squid is running on the same machine as your htb rules then (I think)
>>the only way you can shape incoming traffic from the internet properly
>>is to use imq.
>
>
> I think IMQ needed only if there are not one interface to shape.
>
>
>>I have not used squid - so may be wrong, but the patches will let you
>>classify hits so they can be let through at lan speed. But what about
>>misses - I assume that squid will connect to the internet and fetch the
>>data unlimited even if they then get served to the lan at restricted speed.
>>
>
>
>
> Inet <-----(one for all src)NAT<--(MISSES)---(src 192.168.90.0/28 dst 'real Inet IP')Squid<---(HITS+MISSES)---hosts
>
> Inet ----->(one for all dst)NAT--(MISSES)--->(dst 192.168.90.0/28 src 'real Inet IP')Squid---(HITS+MISSES)--->hosts
>
> The last not fully right... But clenly illustrates the idea.
>
> You can simply shape the MISSES on one interface...
>
Well remember I don't use squid so don't really know, but I imagine that
all lan connections on the relevant ports go to squid and squid then
makes seperate connections to the internet if required. So all traffic
headed from the internet to squid will have the dst IP of the internet
interface even if you hook imq after (de)NAT other traffic will have
local dst addresses.
Andy.
_______________________________________________
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 19:41 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
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 [this message]
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=4296266C.3050902@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.