All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dmytro O. Redchuk" <dor@ldc.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc class class id problem Limitation
Date: Thu, 12 Jan 2006 15:08:07 +0000	[thread overview]
Message-ID: <20060112150806.GE4408@ldc.net> (raw)
In-Reply-To: <6.2.1.2.0.20060112201315.05709bd8@147.202.41.46>

On Thu, Jan 12, 2006 at 08:19:44PM +0530, amit pasari wrote:
> Hello,
> I have been working  on tc class . But when the classid reaches 5 digit , 
> it DOES NOT ACCEPT THAT ...
> see the example below ::
> tc class add dev eth0 parent 10:36 classid 10:13310 cbq bandwidth 10Mbit 
> rate 32Kbit allot 1514 weight 3.2Kbit prio 5 maxburst 20 avpkt 1000 bounded
> 
> See the bold digit !! this command doesn't work  , but if i use with 4 
> digit then it works :
> tc class add dev eth0 parent 10:36 classid 10:1331 cbq bandwidth 10Mbit 
> rate 32Kbit allot 1514 weight 3.2Kbit prio 5 maxburst 20 avpkt 1000 bounded
> 
> Can anyone tell me is it a limitation or what , and can i over come it ??
Four.
In hex.

0001 - FFFF (FFFE?) I guess.

> URGENT HELP IS REQUIRED !!
> Thanks in advance .
> 
> amit pasari 

> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc


-- 
  _,-=._              /|_/|
  `-.}   `=._,.-=-._.,  @ @._,
     `._ _,-.   )      _,.-'
        `    G.m-"^m`m'        Dmytro O. Redchuk


XMMS: 

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      reply	other threads:[~2006-01-12 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 14:51 [LARTC] tc class class id problem Limitation amit pasari
2006-01-12 15:08 ` Dmytro O. Redchuk [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=20060112150806.GE4408@ldc.net \
    --to=dor@ldc.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.