From: "Wennie V. Lagmay" <wlagmay@yanbulink.net>
To: Jason Opperisano <opie@817west.com>, netfilter@lists.netfilter.org
Subject: Re: Iptables as packet shaper
Date: Sun, 15 May 2005 08:58:28 +0300 [thread overview]
Message-ID: <000501c55913$1d8da540$f00aa9c0@winxp> (raw)
In-Reply-To: 20050514153904.GA24505@bender.817west.com
If im not mistaken TC require iptroute 2. If im already using iptables for
my routing, firewall and NAT, do I need to disable iptables for iproute2 or
iptables and iproutes works hand in hand
thanks,
wennie
----- Original Message -----
From: "Jason Opperisano" <opie@817west.com>
To: <netfilter@lists.netfilter.org>
Sent: Saturday, May 14, 2005 6:39 PM
Subject: Re: Iptables as packet shaper
> On Sat, May 14, 2005 at 02:51:55PM +0300, Wennie V. Lagmay wrote:
>> Hi all,
>>
>> Im using iptables to filter, translate IP address and forward traffic,
>> Im
>> using squid delay_pool to limit client access per user and per network,
>> but
>> im having a limitation with the squid delay_pool. I want to have a packet
>> shaper that can can allow my user to have 32 kbps during peer time and
>> 256
>> during off peek time. Delay_pool is not capable of that. Can IPTABLES do
>> this kind of shaping?
>
> no--bandwidth management is not the job of iptables, it is the job of tc
> from the iproute2 package. details are at:
>
> http://lartc.org/howto/lartc.qdisc.html
>
> lartc also has their own ML:
>
> http://lartc.org/#mailinglist
>
> -j
>
> --
> "Peter: Wow, is that really the blood of Christ?
> Preacher: Yes, it is.
> Peter: Holy crap, that guy must've been wasted 24 hours a day."
> --Family Guy
>
next prev parent reply other threads:[~2005-05-15 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 11:51 Iptables as packet shaper Wennie V. Lagmay
2005-05-14 15:39 ` Jason Opperisano
2005-05-15 5:58 ` Wennie V. Lagmay [this message]
2005-05-15 6:48 ` Robert Vangel
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='000501c55913$1d8da540$f00aa9c0@winxp' \
--to=wlagmay@yanbulink.net \
--cc=netfilter@lists.netfilter.org \
--cc=opie@817west.com \
/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.