From: "Simo" <simo@mix4web.de>
To: lartc@vger.kernel.org
Subject: [LARTC] problem with prio qdisc and tcng
Date: Wed, 25 Apr 2007 01:12:52 +0000 [thread overview]
Message-ID: <000001c786d6$d97c6500$8c752f00$@de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3134 bytes --]
Hello Mailing list,
I have a problem with the prio qdisc and I don´t know what is wrong in my
configuration
This ist a sample configuration and looks like this:
#include "fields.tc"
#include "ports.tc"
#define X16(i) i i i i i i i i i i i i i i i i
dev ppp0 {
dsmark {
prio(bands 6, priomap X16($be)) {
class if ip_proto == IPPROTO_UDP;
class if tcp_dport == PORT_TELNET;
class if tcp_dport == PORT_HTTP;
class if tcp_dport == PORT_SMTP;
class if ip_dst == 10.0.10.10;
$be = class(6);
}
}
}
The tc-Code looks like this:
# ================================ Device ppp0
================================
tc qdisc add dev ppp0 handle 1:0 root dsmark indices 64 set_tc_index
tc qdisc add dev ppp0 handle 2:0 parent 1:0 prio bands 6 priomap 5 5 5 5 5 5
5 5 5 5 5 5 5 5 5 5
tc filter add dev ppp0 parent 2:0 protocol all prio 1 u32 match u8 0x11 0xff
at 9 classid 2:1
tc filter add dev ppp0 parent 2:0 protocol all prio 1 handle 1:0:0 u32
divisor 1
tc filter add dev ppp0 parent 2:0 protocol all prio 1 u32 match u8 0x6 0xff
at 9 offset at 0 mask 0f00 shift 6 eat link 1:0:0
tc filter add dev ppp0 parent 2:0 protocol all prio 1 handle 1:0:1 u32 ht
1:0:0 match u16 0x17 0xffff at 2 classid 2:2
tc filter add dev ppp0 parent 2:0 protocol all prio 1 handle 2:0:0 u32
divisor 1
tc filter add dev ppp0 parent 2:0 protocol all prio 1 u32 match u8 0x6 0xff
at 9 offset at 0 mask 0f00 shift 6 eat link 2:0:0
tc filter add dev ppp0 parent 2:0 protocol all prio 1 handle 2:0:1 u32 ht
2:0:0 match u16 0x50 0xffff at 2 classid 2:3
tc filter add dev ppp0 parent 2:0 protocol all prio 1 handle 3:0:0 u32
divisor 1
tc filter add dev ppp0 parent 2:0 protocol all prio 1 u32 match u8 0x6 0xff
at 9 offset at 0 mask 0f00 shift 6 eat link 3:0:0
tc filter add dev ppp0 parent 2:0 protocol all prio 1 handle 3:0:1 u32 ht
3:0:0 match u16 0x19 0xffff at 2 classid 2:4
tc filter add dev ppp0 parent 2:0 protocol all prio 1 u32 match u32
0xa000a0a 0xffffffff at 16 classid 2:5
tc filter add dev ppp0 parent 1:0 protocol all prio 1 tcindex mask 0xfc
shift 2
but when i execute the script and invoke: tc s class show dev ppp0 I
don´t see any Pakets, that have been enqueued or sent.
pc1:/etc/tcng# tc -s class show dev ppp0
class prio 2:1 parent 2:
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
class prio 2:2 parent 2:
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
class prio 2:3 parent 2:
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
class prio 2:4 parent 2:
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
class prio 2:5 parent 2:
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
class prio 2:6 parent 2:
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
----------------------------------------------------------------------------
-----------------------------------------------------------------
In a world without walls who needs gates and windows?
[-- Attachment #1.2: Type: text/html, Size: 12494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2007-04-25 1:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000001c786d6$d97c6500$8c752f00$@de' \
--to=simo@mix4web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox