From: Patrick Nagelschmidt <dto@gmx.net>
To: lartc@vger.kernel.org
Subject: [LARTC] problem with the howto sample
Date: Thu, 06 Dec 2001 22:14:01 +0000 [thread overview]
Message-ID: <marc-lartc-100767692924897@msgid-missing> (raw)
after reading the new howto i wanted to rewrite my QoS-script, now that most parameters lost their mysteriousness. while rewriting i gave some classes new classid's which led to 'RTNETLINK answers: Invalid argument'. i decided to try the sample from the howto first, but got the same problem:
Sample configuration
This configuration limits webserver traffic to 5mbit and smtp traffic to 3 mbit, and limits the sum to 5mbit:
[...]
# tc class add dev eth0 parent 1:1 classid 10: cbq bandwidth 100Mbit \
rate 5Mbit weight 0.5Mbit prio 5 allot 1514 cell 8 maxburst 20 \
avpkt 1000 bounded
the above leads to an Invalid argument. it seems that tc doesnt like the classid 10: (at least the error disappears if i change it to e.g. 1:2).
have i done something wrong or is it an error in the example? this problem leads me also to the next question:
is the naming of classes essential for building them correctly? is parent 1:1 classid 10:0 somehow different from parent 1:1 classid 1:2? up to now i thought classid was only a name and the parent would be enough to make the classes' positions in the tree unambiguously...
regards,
Patrick
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-12-06 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 22:14 Patrick Nagelschmidt [this message]
2001-12-06 22:52 ` [LARTC] problem with the howto sample bert hubert
2001-12-06 23:14 ` Patrick Nagelschmidt
2001-12-06 23:19 ` bert hubert
2001-12-07 0:17 ` Patrick Nagelschmidt
2001-12-07 4:35 ` Michael T. Babcock
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-100767692924897@msgid-missing \
--to=dto@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox