From: "Radosław Łoboda" <p0wer@tl.krakow.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and bridge...
Date: Wed, 21 Aug 2002 14:59:37 +0000 [thread overview]
Message-ID: <marc-lartc-102994197721824@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102990531021943@msgid-missing>
On Tue, 20 Aug 2002, zain arrifa'i wrote:
> does anyone know about HTB shaping in a bridging
> machine?
> I currently run my shaper box as bridge and something
> is going strange, such as a class cannot send at rate
> it supposed to.
> I mean if anyone know something about bridging and its
> htb shaping behavior.
> thanks in advance.
I don't know about HTB but I had such configuration:
,------------------------------.
| ,-- eth0 -+--> Seg1
INET ----+-> ppp0 -- ROUTER --+ (bridge)|
| (fwall) `-- eth1 -+--> Seg2
`------------------------------'
and I succeded in firewalling and shaping one of the segments with CBQ
(just limiting to some rate, in this example INET\x192kbit, seg1dkbit).
It just worked, of course after applying the correct patches fr bridge
firewalling into the kernel...
--
##########################################
# | p0wer | #
# __ | GG#1877248 | #
# (oo) | p0wer@bojko.eu.org | #
# / \/ \ Go away or I will replace you #
# `V__V' with a very small shell script. #
##########################################
_______________________________________________
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-08-21 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 4:47 [LARTC] HTB and bridge zain arrifa'i
2002-08-21 14:59 ` Radosław Łoboda [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-20 7:33 [LARTC] htb " asko askeltaja
2003-02-20 10:44 ` deepak singhal
2006-11-17 3:50 ` [LARTC] HTB " alan tan
2006-11-17 3:58 ` alan tan
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-102994197721824@msgid-missing \
--to=p0wer@tl.krakow.pl \
--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.