From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Squid + shaping question
Date: Fri, 09 Apr 2004 12:10:41 +0000 [thread overview]
Message-ID: <407692C1.4010908@dsl.pipex.com> (raw)
In-Reply-To: <20040408003240.77A644456@outpost.ds9a.nl>
Teodor Yantchev wrote:
> Hi folks,
>
> So, I have a pretty simple setup - a linux router machine running as a
> firewall/router for a small neighborhood LAN (approx 20 machines). I also
> have squid running on the box in non-transparent mode, and also I have set
> up NAT for TCP/UDP ports above 1024 for all clients and SSH/POP/SMTP/CVS
> NAT'd for selected ones based on MAC filtering. No hosts whatsoever can
> access ports 80 and 443 without going through squid. The uplink to the
> internet is 512kbit/s downstream and 64kbit/s upstream cable modem connected
> on eth1 (LAN on eth0, no DMZ).
> When the LAN started to grow from a few well known friends of mine to more
> people I didn't know so well 'social shaping' stopped working for us - bulk
> downloaders started to saturate the link so badly that I even couldn't use
> acceptably ssh from outside. So - the usual solution - www.lartc.org.
> I did a lot of reading on the topic (This really got me interested in) and
> finally ended up installing a self-modified version of wondershaper on the
> external interface. This did solve the problem of me having usable ssh from
> my office to the router machine, and the ingress qdisc partially solved the
> problem of the downlink being fairly distributed between all incoming
> connections - but as most of you know this is a half-baked bread. What I
> think should be done is shaping the internal interface - BUT - the squid
> in-between causes trouble.
> So the question is - How to differentiate between traffic served from
> squid's cache and traffic squid got directly from the internet ?
> Shaping/policing all web traffic negates the benefits of having a caching
> proxy pretty much.
> After lots of googling and reading(at one point I was ready to completely
> forget squid) a came up with the following alternatives, both found on the
> FAQ section of www.docum.org - 'SQUID zero penalty for HIT traffic patch' by
> a fellow bulgarian Marin Stavrev, and a patch giving you the ability to 'use
> ACL lists to put packets in classes' by a guy named Patrick.
> I'd like to ask you for your experiences with those, which one is better,
> any other alternatives you know of and of course general
> recipes/recommendations for solving my problem.
You could shape on just the internet link using IMQ with the NAT patch
to control traffic from the inet to squid.
You can already shape up traffic - 64K for 20 machines isn't nice, but
you can still do it if interactive traffic is less.
Given the other answers - I may be missing something, I've never used
squid, but can shape local destined bittorrent OK.
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-04-09 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 0:25 [LARTC] Squid + shaping question Teodor Yantchev
2004-04-08 17:38 ` Evgeni Gechev
2004-04-08 20:11 ` Radoslav Kolev
2004-04-09 12:10 ` Andy Furniss [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=407692C1.4010908@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.