From: "Adam Towarnyckyj" <adamt@commspeed.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Class ID limits
Date: Thu, 17 Jun 2004 16:05:26 +0000 [thread overview]
Message-ID: <002801c45484$e7539f90$903113d8@uranus> (raw)
In-Reply-To: <00b801c453dd$5f4c4bd0$903113d8@uranus>
Thank you very much for your help. I couldn't seem to find that anywhere
in the documentation. Maybe I wasn't looking in the right place.
Anyways, thanks again.
Adam
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]
On Behalf Of Nikolay Datchev
Sent: Thursday, June 17, 2004 12:54 AM
To: Catalin BOIE
Cc: Adam Towarnyckyj; lartc@mailman.ds9a.nl
Subject: Re: [LARTC] Class ID limits
> > 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!
>
> Class parameters to tc are hexa numbers so you can use from x:1 to
x:ffff,
> meaning 65535 classes.
>
And note that you must supply the classid in hex. Try searching google
for
a small tool like dec2hex, which converts decimal numbers to hex.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-06-17 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 20:06 [LARTC] Class ID limits Adam Towarnyckyj
2004-06-17 7:20 ` Catalin BOIE
2004-06-17 7:53 ` Nikolay Datchev
2004-06-17 8:00 ` Nikolay Datchev
2004-06-17 16:05 ` Adam Towarnyckyj [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='002801c45484$e7539f90$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