Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Adam Towarnyckyj" <adamt@commspeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Class ID limits
Date: Wed, 16 Jun 2004 20:06:12 +0000	[thread overview]
Message-ID: <00b801c453dd$5f4c4bd0$903113d8@uranus> (raw)

Hey everyone,
	I had a question about the class id's using the TC command. I'm
using a command that looks something like this:

tc class add dev eth1 parent 10: classid 10:$variable cbq bandwidth
200Mbit rate 512Kbit allot 1514 prio 5 maxburst 20 avpkt 1000 bounded

That's just an example. My problem is I'm guessing the $variable is not
allowed to be anything over 9999. I'm getting an error when I run that
command with anything over 4 digits as a $variable. The error is:

RTNETLINK answers: Invalid argument

I've also tried just entering that in at the command prompt and using
10000 as the variable and that error shows up.

I actually have a few questions. First, am I right in assuming this or
is the reason something totally different? And, if I'm right, is there
any way around the limit other than creating a new qdisc? I'm trying to
use a number we have set up in our database and sometimes it goes into
the 5 digit range. Any help would be greatly appreciated. Thanks!


Adam Towarnyckyj
Network Operations
CommSpeed AZ, LLC
http://www.commspeed.net/
Phone: 928-772-1111 x131
 


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-06-16 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 20:06 Adam Towarnyckyj [this message]
2004-06-17  7:20 ` [LARTC] Class ID limits Catalin BOIE
2004-06-17  7:53 ` Nikolay Datchev
2004-06-17  8:00 ` Nikolay Datchev
2004-06-17 16:05 ` Adam Towarnyckyj

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='00b801c453dd$5f4c4bd0$903113d8@uranus' \
    --to=adamt@commspeed.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