From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB burstable for 2 interface , how ?
Date: Thu, 03 Jul 2003 09:12:23 +0000 [thread overview]
Message-ID: <marc-lartc-105722416003189@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105722285902235@msgid-missing>
On Thursday 03 July 2003 10:56, rio@martin.mu wrote:
> Dear folks,
> Here goes my bandwidth manager:
>
> INTERNET
>
> |eth0 202.14.41.1
>
> BW.Manager
>
> | +----eth1----192.168.1.0/24
>
> +------eth2----192.168.2.0/24
>
> Total incoming bandwidth to eth0 is 1024kbps
> should be shared to eth1 and eth2, which mean each get 512Kbps and
> burstable to 1024Kbps if other host is idle.
>
> My question is how do i apply HTB to these situation ?
> As far as i know eth1 and eth2 should be define as parent and cannot be as
> children.
Indeed. What you can do is use imq and add a imq device to your eth0.
Redirect all incoming traffic to it and a htb qdisc to the imq device.
Create 2 classes : one for eth1 and one for eth2. And voila, eth1 and eth2
can share 1024 kbps.
You can have a problem splitting the traffic in the classes because you don't
know the src address when the packets enters your shaper.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-07-03 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 8:56 [LARTC] HTB burstable for 2 interface , how ? rio
2003-07-03 9:12 ` Stef Coene [this message]
2003-07-03 9:12 ` ???????? ?????
2003-07-03 9:18 ` Martin Devera
2003-07-03 9:38 ` rio
2003-07-03 9:50 ` Stef Coene
2003-07-03 11:45 ` Joel
2003-07-04 16:39 ` Don Cohen
2003-07-07 3:54 ` Leonardo Balliache
2003-07-09 3:22 ` Leonardo Balliache
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-105722416003189@msgid-missing \
--to=stef.coene@docum.org \
--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.