All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Surda <surda@shurdix.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Per user bandwidth limiting ..for small ISP.using Squid
Date: Fri, 13 Jan 2006 15:58:19 +0000	[thread overview]
Message-ID: <43C7CE1B.7080600@shurdix.com> (raw)
In-Reply-To: <a86cb2470601130716g3fde7aebq7bd143116792ab3e@mail.gmail.com>

Madhava Rayudu schrieb:

> Sir,

Hello,

>  I am a small ISP in rural India distributing 1 MB
> link to 200 people.

...

> Squid saves me around 35% of bandwidth and hence I can
> not afford not to use it.


I hope people won't mind if I mention my project again:
http://www.shurdix.org

For some time it was successfully used on a network with 8MBit link and 
1400 users (although the peak of simultaneously active users was "only" 
slightly above 700). So it should be able to work in your situation.

Your situation is however special because you have squid. Combining 
squid and tc is problematic. 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. Squid including 
the tproxy patch can be found in the optional package for shurdix (I'll 
document it on the wiki page if you are interested).

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.

I would like to stress again however that combining tproxied squid and 
tc isn't easy and is poorly documented (but possible and it works). YMMV.

> Rayudu.

Yours sincerely,
Peter

-- 
http://www.shurdix.org - Linux distribution for routers and firewalls

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

  reply	other threads:[~2006-01-13 15:58 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 [this message]
2006-01-14 15:21 ` Andreas Klauer
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=43C7CE1B.7080600@shurdix.com \
    --to=surda@shurdix.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.