From: Radoslaw Stachowiak <radek@alter.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple rate limited networks and transparent http proxy - tricky problem
Date: Mon, 23 Dec 2002 22:16:41 +0000 [thread overview]
Message-ID: <marc-lartc-104068186110925@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104067934909162@msgid-missing>
*** Aaron A. Wolfe <aaron@aaronwolfe.com> [16:40 Mon 23.Dec]:
> My "problem" is that of course the rate limiting applies to *all*
> traffic going out the internal interfaces, so even objects that are in
> the squid cache are given to the clients at a fairly slow speed.
You can achieve results by using iptables mark facility to mark packets
which are passing by your router (from internet) and are not for Your
router, and than use this mark value to distinguish if packet is local
or not (fw filter).
while solving your orginal problem it leaves one more. when client try
to fetch object which is not in squid cache, squid will fetch it with
full bandwith and serve for client also with full bandwitch.
here you should make decision:
1. this is ok behaviour (although little unfair) because such
fetched-at-full-speed objects are ready for other clients (also on full speed)
2. this is not ok, and You have to cbq (or rather IMQ) squid which is
hard task because there is one squid for all clients. you can try use
hbt and grant for squid unused bandwith from all clients by proper
classes schema.
addidtional to 1. you can 'enhance' it by using squid delaypools to help
it to be little more fair.
perfect solution is to hack squid to mark its packets based on HIT/MISS.
.radek.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-12-23 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 21:40 [LARTC] Multiple rate limited networks and transparent http proxy - tricky problem Aaron A. Wolfe
2002-12-23 22:16 ` Radoslaw Stachowiak [this message]
2002-12-24 4:37 ` Greg Scott
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-104068186110925@msgid-missing \
--to=radek@alter.pl \
--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.