From: Lawrence MacIntyre <lpz@ornl.gov>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What's wrong here? HELP PLEASE!!!!
Date: Wed, 08 Oct 2003 12:00:37 +0000 [thread overview]
Message-ID: <marc-lartc-106561458323700@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106556129015179@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 4145 bytes --]
I'm grasping at straws here, but is it possible that you put your new tc
in, for example, /usr/local/sbin/tc and your script is calling the
original version in /sbin/tc ?
You shouldn't have to patch the kernel, and the patched tc should work.
When you run the script, is the first error (RTNETLINK answers: No such
file or directory) coming from the first line in your script (/sbin/tc
qdisc add dev eth1 root handle 1: htb default 10)? It would be helpful
if you could give us the errors interspersed with the commands If you
add sh -x to the beginning of the command running the script, it will do
that.
example:
[root@castor root]# sh -x /etc/tc.conf
+ /usr/local/bin/tc qdisc add dev eth0 root handle 1: htb default 12
+ /usr/local/bin/tc class add dev eth0 parent 1: classid 1:1 htb rate
13Mbit ceil 10Mbit
+ /usr/local/bin/tc class add dev eth0 parent 1:1 classid 1:10 htb rate
12Mbit ceil 10Mbit
+ /usr/local/bin/tc class add dev eth0 parent 1:1 classid 1:11 htb rate
1Mbit ceil 10Mbit
+ /usr/local/bin/tc qdisc add dev eth0 parent 1:10 handle 20: sfq
+ /usr/local/bin/tc qdisc add dev eth0 parent 1:11 handle 30: sfq
+ /usr/local/bin/tc filter add dev eth0 protocol ip parent 1:0 prio 1
u32 match
ip dport 1234 0xffff flowid 1:10
+ /usr/local/bin/tc filter add dev eth0 protocol ip parent 1:0 prio 1
u32 match
ip dport 5001 0xffff flowid 1:11
When I try the old tc on my machine (red hat 8.0), I get this:
tc qdisc add dev eth0 root handle 1: htb default 12
Unknown qdisc "htb", hence option "default" is unparsable
Which version of linux are you using?
On Tue, 2003-10-07 at 17:13, Alex wrote:
> (this is a repost, nobody said anything about this so maybe it did not
> go
> throu the list)
> I downloaded iproute2-2.4.7-now-ss010824.tar.gz and I did patched tc
> with
> the htb3.6_tc.diff from htb3.6-020525.tgz and when I try to use a htb
> script
> I get just errors. I did not patch the kernel, since I use kernel
> 2.4.22 and
> I saw on - HTB Homepage that I need to patch it only if I run version
> 2.4.20
> or earlier. Do also need the kernel patch ? Or maybe is something else
> wrong? (I also used the precompiled "tc" but the situation is the
> same)
>
> Errors:
> -------
> RTNETLINK answers: No such file or directory
> Deleted old root disk on eth1
> Unknown filter "flowid", hence option "1:10" is unparsable
> Unknown filter "flowid", hence option "1:2" is unparsable
> RTNETLINK answers: Invalid argument
> RTNETLINK answers: Invalid argument
> RTNETLINK answers: Invalid argument
> RTNETLINK answers: Invalid argument
> .....etc (same error over and over...)
>
> Part of my script (the full script is accesible on
> http://retea.hostingcenter.ro/htb.txt ..is too long to post here) :
> -------
> /sbin/tc qdisc add dev eth1 root handle 1: htb default 10
> /sbin/tc class add dev eth1 parent 1: classid 1:1 htb rate 10mbit
>
> /sbin/tc class add dev eth1 parent 1:1 classid 1:10 htb rate 5mbit
> /sbin/tc filter add dev eth1 protocol ip parent 1:10 prio 5 handle 6
> flowid
> 1:10
>
> /sbin/tc class add dev eth1 parent 1:1 classid 1:2 htb rate 5mbit
> /sbin/tc filter add dev eth1 protocol ip parent 1:10 prio 5 handle 5
> flowid
> 1:2
>
>
> /sbin/tc class add dev eth1 parent 1:10 classid 4:11 htb rate 128kbit
> ceil
> 256kbit prio 5
> /sbin/tc filter add dev eth1 parent 1:10 protocol ip prio 5 u32 match
> ip dst
> 192.168.254.10 flowid 4:11
>
> /sbin/tc class add dev eth1 parent 1:10 classid 4:12 htb rate 128kbit
> ceil
> 256kbit prio 5
> /sbin/tc filter add dev eth1 parent 1:10 protocol ip prio 5 u32 match
> ip dst
> 192.168.254.11 flowid 4:12
>
> ....etc (full script at http://retea.hostingcenter.ro/htb.txt)
>
> Thanks!
>
> Alex
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
--
Lawrence MacIntyre 865.574.8696 lpz@ornl.gov
Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-10-08 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 21:13 [LARTC] What's wrong here? HELP PLEASE!!!! Alex
2003-10-07 22:03 ` Stef Coene
2003-10-08 12:00 ` Lawrence MacIntyre [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=marc-lartc-106561458323700@msgid-missing \
--to=lpz@ornl.gov \
--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.