Displaying 5 results from an estimated 5 matches for "htb_classifi".
Did you mean:
htb_classify
2004 Sep 09
0
Setting priority in userspace gets ignored
Briefly what I am trying to achieve is using the HTB qdisc to handle
traffic generated from
userspace. To achieve this I create a standard Gold/Silver/Bronze
configuration as follows;
tc qdisc add dev eth0 root handle 1: htb default 12
tc class add dev eth0 parent 1: classid 1:1 htb rate 100mbit
tc class add dev eth0 parent 1:1 classid 1:10 htb rate 1mbit ceil 100mbit
tc class add dev eth0
2004 Jun 18
1
Help:how to generate different packets?souce code explanation?
Hi,All
I setup traffic control configuration with HTB this way:
1: root HTB qdisc
|
1:1 HTB class rate 1024kbit
|
/-----+-----+-----+------+-----\
1:10 1:20 1:30 1:40 1:50 1:60
EF AF41 AF31 AF21 AF11 BE
and alloct different bandwidth to these PHBs(queues).So which tool would I use to generate these packets at the same to for
2006 Jan 26
0
Profiling hotspots in my tc filter ruleset
Hi,
after I saw that my machine was having problems to forward
more than 200 Mbit/s, I decided to profile the kernel and
find out the hotspots. This is what I found:
[...]
1028 bridge.ko __br_forward
1033 bridge.ko br_nf_forward_finish
1074 bridge.ko ip_sabotage_in
1119 ebtable_filter.ko ebt_hook
1177 sky2.ko
2006 Aug 02
10
[PATCH 0/6] htb: cleanup
The HTB scheduler code is a mess, this patch set does some basic
house cleaning. The first four should cause no code change, but the
last two need more testing.
--
Stephen Hemminger <shemminger@osdl.org>
"And in the Packet there writ down that doome"
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
2006 May 19
25
iptables CLASSIFY and MARK not working?
I have to match my packets based on MAC address, which I cannot do in
the POSTROUTING chain, so I do it in PREROUTING using MARK. Then, I
match on the MARK in the POSTROUTING chain to do a CLASSIFY. But this
does not seem to work:
wireless-r1 bwlimit # iptables -L -v -n -t mangle
Chain PREROUTING (policy ACCEPT 3353K packets, 941M bytes)
pkts bytes target prot opt in out source