Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Per user bandwidth limiting ..for small ISP.using Squid
Date: Sat, 14 Jan 2006 15:21:10 +0000	[thread overview]
Message-ID: <20060114152110.GA10585@EIS> (raw)
In-Reply-To: <a86cb2470601130716g3fde7aebq7bd143116792ab3e@mail.gmail.com>

On Fri, Jan 13, 2006 at 04:58:19PM +0100, Peter Surda wrote:
> I hope people won't mind if I mention my project again:
> http://www.shurdix.org

We're happy to receive any reply at all, really... :-)

> Your situation is however special because you have squid. Combining 
> squid and tc is problematic.

I agree; so far I haven't been able to shape squid traffic 
the way I want it to. However, shouldn't rshaper suffer from the 
same issues? It should at least be possible to do something 
similar to rshaper using tc.

> However, there were some kind guys who designed the "tproxy" iptables 
> extension, which can help you. It isn't easy to setup and if you have 
> NAT you need 2 separate machines (one doing the NAT and one running 
> the squid), but is doable. This way tc will see squid's traffic with 
> the IP of the real client.

These are about the most interesting lines I've seen on this topic. 
However, I'm in a small home network situation, so even having just 
one dedicated linux machine is luxury. So any solution that requires 
separate machines is not feasible for me.

> My recommendation for your situation would be something like this:
> - keep your router, let it do NAT and perhaps a minimal firewall
> - get a second machine, put it between the router and the LAN, and 
> install shurdix there
> - configure it to use TC and Squid (and optionally IP accounting and/or 
> firewall if you like). No delay pools necessary.

Other possibilities are:
- Never touch a running system. (If it works, why not leave as is?)
- Find out how exactly rshaper limits and/or distributes
  up- and download bandwidth for
    * User <-> Internet
    * User <-> User
    * Internet <-> Squid (and other caches, DNS etc.)
    * Squid (and others?) <-> User
  and use this information to build a tc class tree.
- If you want to keep rshaper, port it to 2.6 by yourself ;-)

Regards,
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-01-14 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 15:28 [LARTC] Per user bandwidth limiting ..for small ISP.using Squid Madhava Rayudu
2006-01-13 15:58 ` Peter Surda
2006-01-14 15:21 ` Andreas Klauer [this message]
2006-01-14 21:43 ` Peter Surda
2006-01-15  7:58 ` Madhava Rayudu
2006-01-17 17:38 ` Madhava Rayudu
2006-01-17 20:14 ` Peter Surda

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=20060114152110.GA10585@EIS \
    --to=andreas.klauer@metamorpher.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox