From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc qdisc replace failing
Date: Sun, 06 Nov 2005 17:42:06 +0000 [thread overview]
Message-ID: <436E406E.DC8C4E51@iswest.com> (raw)
In-Reply-To: <200511061553.59671.lartc-337@ccp.com.au>
Lee Sanders wrote:
>
> Hi,
>
> Having issues getting a replace command working correctly. The error reported
> is "RTNETLINK answers: Invalid argument" which isn't descriptive or helpful.
>
> The command i'm running is:
>
> tc qdisc replace dev ppp0 parent 8001:D handle D: tbf rate 5Kbit burst 5kb
> latency 70ms
>
> The idea being to replace an sfq with handle D and hopefully limit a certain
> user in my WRR class. If I delete the qdisc first and add with the below line
> it works.
>
> tc qdisc del dev ppp0 parent 8001:D handle D:
> tc qdisc add dev ppp0 parent 8001:D handle D: tbf rate 5Kbit burst 1540
> latency 70ms
>
> Anyone see what I'm doing wrong ?
>
> :Lee
I believe that replace is still broken so, if I'm correct, the answer
is, "replace does not work."
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-11-06 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 7:53 [LARTC] tc qdisc replace failing Lee Sanders
2005-11-06 17:42 ` gypsy [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=436E406E.DC8C4E51@iswest.com \
--to=gypsy@iswest.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