From: "Gavin White" <gavin@raha.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] squid + tc
Date: Wed, 22 May 2002 08:36:12 +0000 [thread overview]
Message-ID: <marc-lartc-102205665030702@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102205109325878@msgid-missing>
oh well, just wondered if there was a way to get squid to keep the original
IP.
I'm currently working on a fully automated mac address authentication,
bandwidth control thing for WISPS - it takes a csv from rodopi and modifies
it's iptables and htb rules according to the latest client data. In fact,
we're starting to migrate today. If anyone wants to take a look at the
script, mail me and I'd be glad to send it.
Gavin
----- Original Message -----
From: "Stef Coene" <stef.coene@docum.org>
To: "Gavin White" <gavin@raha.com>; <LARTC@mailman.ds9a.nl>
Sent: Wednesday, May 22, 2002 10:27 AM
Subject: Re: [LARTC] squid + tc
On Wednesday 22 May 2002 09:00, Gavin White wrote:
> Hello,
>
> I have some htb rules set up to govern download speeds through a linux
box,
> depending on the IP address of the destination machine.
>
> My problem is that when the end users choose to use my squid cache, which
> sits before the htb machine (and has to be there), the htb machine thinks
> the traffic is going to/from the squid box, so nullifying all my
bandwidth
> rules.
All squid traffic will have as source address the squid box, so you can't
know who is doing what. But squid can also do bandwidth management. Take a
look at delay pools,
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
**************************************************************
Scanned by MailScan Content-Security and Anti-Virus Software.
Visit http://www.mwti.net for more info on eScan and MailScan.
**************************************************************
**************************************************************
Scanned by MailScan Content-Security and Anti-Virus Software.
Visit http://www.mwti.net for more info on eScan and MailScan.
**************************************************************
_______________________________________________
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-05-22 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 7:00 [LARTC] squid + tc Gavin White
2002-05-22 7:27 ` Stef Coene
2002-05-22 8:36 ` Gavin White [this message]
2002-05-22 8:43 ` Martin Devera
2002-05-22 17:13 ` Andreas Lehrbaum
2002-05-22 18:35 ` Patrick McHardy
2002-05-22 18:57 ` Martin Devera
2002-05-23 2:38 ` Patrick McHardy
2002-05-23 7:04 ` Martin Devera
2002-05-23 13:57 ` Patrick McHardy
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-102205665030702@msgid-missing \
--to=gavin@raha.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