From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What's wrong here? HELP PLEASE!!!!
Date: Tue, 07 Oct 2003 22:03:40 +0000 [thread overview]
Message-ID: <marc-lartc-106556428118535@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106556129015179@msgid-missing>
On Tuesday 07 October 2003 23: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)
Try to add
set -x
to your script on the second line. This will display all commands executed so
you know exactly which command is going wrong.
You miss something in your filter statement. You have to specify the type of
filter you want to use and in your case, that's the fw filter. See lartc.org
and/or docum.org for fw filter examples.
Stef
>
> 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/
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.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-10-07 22:03 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 [this message]
2003-10-08 12:00 ` Lawrence MacIntyre
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-106556428118535@msgid-missing \
--to=stef.coene@docum.org \
--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.