From: "Kristoffer Ottosson" <snowie@klippanlan.net>
To: lartc@vger.kernel.org
Subject: [LARTC] wondershaper problem
Date: Sun, 22 Sep 2002 23:16:07 +0000 [thread overview]
Message-ID: <marc-lartc-103273661225978@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Hi
I have two lucent wlancards and one 3com ethernet card running on my box.
I'm running routing tables with iproute2 in order to route all the packets correctly ... Now I wonder, I should be able to use wondershaper on top of this, right?
When I try to run wondershaper, it does nothing, and gives me lots of error messages ...
The beginning of them are quoted here (output with -x activated in the beginning of the script):
+ DOWNLINK=1024
+ UPLINK=1024
+ DEV=eth1
+ NOPRIOHOSTSRC=80
+ NOPRIOHOSTDST=
+ NOPRIOPORTSRC=
+ NOPRIOPORTDST=
+ '[' '' = status ']'
+ tc qdisc del dev eth1 root
+ tc qdisc del dev eth1 ingress
+ '[' '' = stop ']'
+ tc qdisc add dev eth1 root handle 1: cbq avpkt 1000 bandwidth 10mbit
RTNETLINK answers: Invalid argument
+ tc class add dev eth1 parent 1: classid 1:1 cbq rate 1024kbit allot 1500 prio 5 bounded isolated
RTNETLINK answers: Invalid argument
+ tc class add dev eth1 parent 1:1 classid 1:10 cbq rate 1024kbit allot 1600 prio 1 avpkt 1000
RTNETLINK answers: Invalid argument
+ tc class add dev eth1 parent 1:1 classid 1:20 cbq rate 921kbit allot 1600 prio 2 avpkt 1000
RTNETLINK answers: Invalid argument
+ tc class add dev eth1 parent 1:1 classid 1:30 cbq rate 819kbit allot 1600 prio 2 avpkt 1000
RTNETLINK answers: Invalid argument
and so it continues on every single command-line wondershaper tried to type in.
anybody have a clue, I would be grateful
/Snowi3
[-- Attachment #2: Type: text/html, Size: 2311 bytes --]
next reply other threads:[~2002-09-22 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 23:16 Kristoffer Ottosson [this message]
2002-09-24 13:05 ` [LARTC] wondershaper problem Stef Coene
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-103273661225978@msgid-missing \
--to=snowie@klippanlan.net \
--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.