From: Peter Surda <surda@shurdix.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Per user bandwidth limiting ..for small ISP.using Squid
Date: Sat, 14 Jan 2006 21:43:10 +0000 [thread overview]
Message-ID: <43C9706E.9040005@shurdix.com> (raw)
In-Reply-To: <a86cb2470601130716g3fde7aebq7bd143116792ab3e@mail.gmail.com>
Andreas Klauer schrieb:
>>However, there were some kind guys who designed the "tproxy" iptables
>>extension, which can help you.
>>
(cut)
>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.
>
>
Unfortunately for design reasons, TPROXY and NAT won't work together and
AFAIK there are no plans to change this. I didn't investigate deeply,
but I assume TPROXY uses the fields reserved for NAT for other purposes.
So if you need both NAT and TPROXY, you need 2 boxes (and some hacking
with the routing or arptables or both ;-)).
>Other possibilities are:
>- Never touch a running system. (If it works, why not leave as is?)
>
>
Actually this is a great idea. I admit I didn't read the original post
completely and assumed that a new system is required for some reason.
>- Find out how exactly rshaper limits and/or distributes
>
>
Upon looking at the docs for rshaper, I don't think it distributes
anything (only limits and has no borrowing). This can be done with HTB
(and IMQ). Several years ago I wrote a bandwidth management system for a
small ISP that actually worked somewhat like this (the ISP uses a web
interface to set incoming/outgoing bandwith for individual customers,
and optionally a monthly limit, and cron sets up the HTB rules
automagically). I don't use it personally, Shurdix does fair
distribution only, but I imagine there are people who might have other
requirements. If there is enough interest (and I find the time) I can
polish it and put it for download.
>Regards,
>Andreas Klauer
>
>
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
next prev parent reply other threads:[~2006-01-14 21:43 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
2006-01-14 21:43 ` Peter Surda [this message]
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=43C9706E.9040005@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox