From: "Cain, Joseph" <jcain01@harris.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] prio error
Date: Thu, 12 Jun 2003 20:11:37 +0000 [thread overview]
Message-ID: <marc-lartc-105544872529105@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105544683526692@msgid-missing>
Thanks Stef. I'm a little confused now as to whether
we have all of the needed files. We are running
Redhat 8.0 includes the iproute-2.4.7-5 package.
We complied the kernal with all of the QoS switches
enabled. I cannot determine if Redhat 8.0 includes the
required iproute2+tc package. By searching some
web sites we find a tar file with
iproute2-2.4.7-now-ss020116-try.tar.gz.
Is this already in Redhat 8.0 or do we
need to include this also (also is this
the latest version).
Thanks for the help.
Bibb Cain
-----Original Message-----
From: Stef Coene [mailto:stef.coene@docum.org]
Sent: Thursday, June 12, 2003 3:36 PM
To: Cain, Joseph; Lartc (E-mail)
Cc: Cain, Joseph
Subject: Re: [LARTC] prio error
On Thursday 12 June 2003 21:26, Cain, Joseph wrote:
> I would appreciate any suggestions on the following error.
> The configuration script used to configure prio on a wireless
> interface is the following
>
> #####################################
> tc qdisc del dev wlan0 root
> tc qdisc add dev wlan0 root handle 1: prio
>
>
> We get the following error message:
>
> RTNETLINK :Invalid argument
>
> :Command not found
>
> Any help will be appreciated.
You need the tc binary that can be found in the iproute2+tc package.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-06-12 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 19:26 [LARTC] prio error Cain, Joseph
2003-06-12 19:36 ` Stef Coene
2003-06-12 20:11 ` Cain, Joseph [this message]
2003-06-12 20:50 ` 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-105544872529105@msgid-missing \
--to=jcain01@harris.com \
--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.