From: "Nayak, Ramakrishna" <rnayak@3eti.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] tc errors
Date: Thu, 28 Jun 2001 19:24:46 +0000 [thread overview]
Message-ID: <marc-lartc-99375643803157@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99375152602288@msgid-missing>
I have enabled all the QoS features (except Special RSVP classifier for
IPv6)
Moreover, I had read in the archives that the advanced router options need
to be enabled. I have also enabled all of them.
Any suggestions?
..Ram
-----Original Message-----
From: Wingtung.Leung [mailto:s965817@uia.ua.ac.be]
Sent: Thursday, June 28, 2001 3:05 PM
To: Linux Advanced Router & Traffic Control
Subject: Re: [LARTC] tc errors
On Thu, 28 Jun 2001, Nayak, Ramakrishna wrote:
> tc qdisc add dev eth1 root handle 1: prio bands 3 priomap 0 1 2
>
> I get the error message:
>
> RTNETLINK answers: No such file or directory.
>
> What causes this error? Am I missing anything in the kernel?
Probably. Please check wether you have enabled all QoS parameters in the
current kernel.
(This question comes up far to often, and I don't see it immediatly in the
HOWTO. Anyone to point me to it or fix it?)
--
GnuPG public key: http://www.keyserver.net
fingerprint = A3C4 DE50 712D 4FA8 C564 4D96 5E06 C9CC ECFA 19C5
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
http://ds9a.nl/2.4Routing/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-06-28 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 18:02 [LARTC] tc errors Nayak, Ramakrishna
2001-06-28 19:04 ` Wingtung.Leung
2001-06-28 19:24 ` Nayak, Ramakrishna [this message]
2001-06-28 19:53 ` Wingtung.Leung
2001-06-28 20:02 ` Nikolai Vladychevski
2001-06-28 20:05 ` Nayak, Ramakrishna
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-99375643803157@msgid-missing \
--to=rnayak@3eti.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.