From: "Michal Kolesar" <kolesar@samba.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RTNETLINK answers: Invalid argument
Date: Thu, 21 Jun 2001 07:48:01 +0000 [thread overview]
Message-ID: <marc-lartc-99310940729566@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99294681530099@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
Hello,
is here somebody who can help me?
Where is the best place (mailinglist) for tc troubleshoting?
Or if You need some another information tell me please.
iptables-1.2.2 - from original sources
ip utility, iproute2-ss991023 - from debian potato distribution
I am newbie I dont have experiences with tc.
What is wrong?
Thank You!
kolisko
----- Original Message -----
From: Michal Kolesar
To: lartc@mailman.ds9a.nl
Sent: Tuesday, June 19, 2001 12:38 PM
Subject: [LARTC] RTNETLINK answers: Invalid argument
Hi all,
I have installed 2.4.5 kernel, Debian Potato.
my tc script:
#!/bin/bash
tc qdisc add dev eth1 root handle 20: cbq bandwidth 10Mbit avpkt 1000
echo root
tc class add dev eth1 parent 20:0 classid 20:1 cbq bandwidth 10Mbit rate \
10Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000
echo class
tc class add dev eth1 parent 20:1 classid 20:100 cbq bandwidth 10Mbit rate \
5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \
bounded
echo 100
tc class add dev eth1 parent 20:1 classid 20:200 cbq bandwidth 10Mbit rate \
5Mbit allot 1514 weight 500Kbit prio 5 maxburst 20 avpkt 1000 \
bounded
echo 200
tc qdisc add dev eth1 parent 20:100 sfq quantum 1514b perturb 15
echo sfq100
tc qdisc add dev eth1 parent 20:200 sfq quantum 1514b perturb 15
echo sfq200
tc filter add dev eth1 parent 20:0 prio 25 u32 match ip src 192.168.0.7 flowid 20:100
echo filter100
tc filter add dev eth1 parent 20:0 prio 50 u32 match ip src 192.168.0.0/24 flowid 20:100
echo filter200
after running my tc script:
0 root@gateway:/root# source /etc/init.d/tc
root
class
100
200
sfq100
sfq200
RTNETLINK answers: Invalid argument
filter100
RTNETLINK answers: Invalid argument
filter200
my kernel .config file is attached.
Thank you for help!
kolisko
[-- Attachment #2: Type: text/html, Size: 3776 bytes --]
next prev parent reply other threads:[~2001-06-21 7:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 10:38 [LARTC] RTNETLINK answers: Invalid argument Michal Kolesar
2001-06-21 7:48 ` Michal Kolesar [this message]
2001-06-21 13:43 ` Wingtung.Leung
2001-06-21 13:44 ` Stef Coene
2001-06-21 13:44 ` Stef Coene
2002-03-05 21:38 ` David E. Parks
2002-03-05 21:53 ` bert hubert
2002-03-06 0:52 ` Richardson, Robert
2002-04-22 7:58 ` Alberto.Baragatti
2002-04-29 4:08 ` hanhbnetfilter
2002-04-29 8:08 ` Stef Coene
2003-06-20 7:06 ` [LARTC] RTNETLINK answers: invalid argument Trevor Warren
2003-06-20 18:17 ` Ana Carolina Alonso
2003-06-20 18:56 ` Stef Coene
2003-10-28 12:08 ` [LARTC] RTNETLINK answers: Invalid argument usign wondershaper Luciano Lima
2003-10-28 17:52 ` Stef Coene
2005-04-03 16:54 ` [LARTC] RTNETLINK answers: Invalid argument Nicolas Mailhot
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-99310940729566@msgid-missing \
--to=kolesar@samba.cz \
--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.