From: "Mindaugas Riauba" <mind@bi.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] linux bridging and htb.init / cbq.init
Date: Thu, 19 Dec 2002 09:09:22 +0000 [thread overview]
Message-ID: <marc-lartc-104028905427017@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104028870626803@msgid-missing>
> I'am successful using a linux (2.4.20) bridge and the cbq.init_v0.7
> script for traffic shaping. But I can only use the queuing discipline
> tbf (LEAF=tbf). If I try use queuing discipline sfq or none then tc
> applies the rules but no shaping occurs.
> Is this problem a normal behavior when using bridging ?
>
> I tried to use htb.init (using patched tc binary). It accepts
> the rules but also no shaping occurs (tested with all queuing
> disciplines (LEAF=none|sfq|pfifo).
> Why it doesn't work together with bridging ?
Works for me. View my previous post about exceeding limits. It
applies to this setup with shaping bridged traffic.
Mindaugas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-19 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 9:02 [LARTC] linux bridging and htb.init / cbq.init Maik Ellinger
2002-12-19 9:09 ` Mindaugas Riauba [this message]
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-104028905427017@msgid-missing \
--to=mind@bi.lt \
--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