search for: 600kbit

...through 1:10 has finished. Though I''ve tried assigning different prio''s, 1:10 always gets more bandwidth... Here''s the script that reproduces this behaviour: tc qdisc add dev eth0 root handle 1: htb default 12 r2q 10 tc class add dev eth0 parent 1: classid 1:1 htb rate 600kbit ceil 600kbit tc class add dev eth0 parent 1:1 classid 1:10 htb rate 200kbit ceil 600kbit tc class add dev eth0 parent 1:1 classid 1:11 htb rate 200kbit ceil 600kbit tc class add dev eth0 parent 1:1 classid 1:12 htb rate 200kbit ceil 600kbit tc qdisc add dev eth0 parent 1:10 handle 20: sfq perturb 1...

...#Root htb that all the traffic is going to go through: tc qdisc add dev eth0 root handle 1: htb default 0x42 tc class add dev eth0 parent 1: classid 1:1 htb rate 700kbit burst 6k #Default class for everything not matched by the firewall rules: tc class add dev eth0 parent 1:1 classid 1:42 htb rate 600kbit\ burst 15k prio 0 tc qdisc add dev eth0 parent 1:42 handle 42: sfq perturb 20 #Have the bucket that traffic gets dropped into #be determined by the firewall mark #btw: --set-mark 0xbabeface maps to class id babe:face tc filter add dev eth0 parent 1: p...

...ot;1:1x" leaf be the minimum rate for that leaf and what would happen if there were three leafs "1:10", "1:11", "1:12" all using 300Kbit as their rate, would the bandwidth be shared equally among them even though it is greater than the "1:1" root rate of 600Kbit? 1: 1:1 (600Kbit) 1:10 1:11 1:12 etc... 1:1001,1002... 1:2001,2002... 1:3001,3002... etc... # setting up the main root 1:1 (600Kbit) /sbin/tc class add dev eth1 parent 1: classid 1:1 htb rate 600Kbit # setting up leafs 1:1x /sbin/tc class add dev eth1 parent 1:1 classid 1:1x htb rate x...

Hi all I''m new in this list and i hope to lear and to help if possible. But firt i need help :-( I have this messege in my syslog when my classes and qdiscs goes down. Can any one know what does it mean? Thnx in advance. Yannick Arrimadas Bot Oct 14 16:09:27 pototogorri kernel: HTB init, kernel part version 3.17 Oct 14 16:09:27 pototogorri kernel: Unable to handle kernel paging

To stress the urgency and importance of my questions, I am willing to pay $100 to the first person that can provide me with the scripts/ rules that will work in my SnapGear firewalls that will solve the problems I am having. Please see the following post: Linux QOS and prioritization of real-time data (RTP/VoIP) Thank you!

...Sorry to bother you all. I have a typical problem sharing DSL upstream bandwidth with users. I have 3 types of traffic high-priority, medium-priority and low priority. My upstream rate is 960kbits. Traffic (any priority) can vary in bandwidth from 0 to 960kbits. I have a test setup where I can pump 600kbit of high priority sustained and I have 400kbit of low priority traffic sustained. I expect after the 600kbit high-priority traffic, the remaining 360kbit should be allocated to the medium and low priority. Since I do not have medium-priority everything should go to low-priority traffic. However, I d...

...steals traffic from B''s download, up to its minimum rate. So, after a little while, I should see download B going to 10% = 100Kbit and download A going to 90% = 900Kbit. 3) I stop download B. A goes up to 1Mbit. 4) I apply a client-side limit to A''s download. Now A goes to 600Kbit. 5) I start downloading B again. B cannot steal any bandwidth to A, but it will get all the available bandwidth. So A will stay at 600Kbit, and B will go at 400Kbit. I hope my explanation is clear. Wondershaper does not seem to do this. In fact, when I start downloading A and B, they seem to...

...class queue… all them goes to the default htb queue. Could some one give me some tips? tc qdisc add dev eth1 root handle 1: htb default 13 tc class add dev eth1 parent 1: classid 1:1 htb rate 1Mbit ceil 1Mbit tc class add dev eth1 parent 1:1 classid 1:10 htb rate 400kbit ceil 600kbit prio 0 tc class add dev eth1 parent 1:1 classid 1:11 htb rate 300kbit ceil 800kbit prio 1 tc class add dev eth1 parent 1:1 classid 1:12 htb rate 200kbit ceil 700kbit prio 2 tc class add dev eth1 parent 1:1 classid 1:13 htb rate 100kbit ceil 600kbit prio 2 tc qdisc add dev eth1 parent 1:10 ha...

Hi, I am currently using a 2.4 kernel with multipath routing patch v5 to send outgoing packets in a 1:1 ratio over two lines, however the lines do not actually have equal upstream bandwidth, one has 800kbit and the other 600kbit, so ideally I would like to send packets in a 4:3 ratio, is there anything in 2.6 or a patch for 2.4 that could be used to do that? I tried this ugly hack but it didn''t seem to work: ip route add default src my.ip.add.res equalize nexthop via a.a.a.a weight 1 nexthop via b.b.b.b weight...

...1: htb tc class add dev eth0 parent 1:0 classid 1:1 htb rate 2000Kbit ceil 2000kbit tc class add dev eth0 parent 1:1 classid 1:2 htb rate 1200Kbit ceil 2000kbit tc class add dev eth0parent 1:1 classid 1:3 htb rate 800Kbit ceil 2000kbit tc class add dev eth0 parent 1:2 classid 1:21 htb rate 600Kbit ceil 2000kbit tc class add dev eth0 parent 1:2 classid 1:22 htb rate 300Kbit ceil 2000kbit tc class add dev eth0 parent 1:2 classid 1:23 htb rate 200Kbit ceil 2000kbit tc class add dev eth0 parent 1:2 classid 1:24 htb rate 100Kbit ceil 2000kbit tc class add dev eth0 parent 1:3 classid 1:31...

Sorry I pressed the wrong key and sent the message too early... > -----Ursprüngliche Nachricht----- > Von: Philipp Leusmann [mailto:philipp.leusmann@rwth-aachen.de] > Gesendet: Mittwoch, 8. November 2006 12:53 > An: ''lartc@mailman.ds9a.nl'' > Betreff: Why did I need strange ceiling settings? > > Hi all, > > I recently installed traffic shaping on my

...ssification using the PRIO qdisc and i am having a few problems. I have a root htb class: tc qdisc add dev imq0 root handle 1: htb default 255 r2q 1 tc class add dev imq0 parent 1: classid 1:1 htb rate 768kbit and a child PRIO tc class add dev imq0 parent 1:1 classid 1:99 htb rate 96kbit ceil 600kbit prio 0 tc qdisc add dev imq0 parent 1:99 prio tc filter add dev imq0 parent 1: protocol ip prio 7 u32 match ip dst 192.168.1.99 flowid 1:99 the result is: # tc - s class ls dev imq0 class htb 1:1 root rate 768000bit ceil 768000bit burst 1599b cburst 1599b Sent 2451 bytes 22 pkt (dropped 0,...

...9;m really stumped. This is what happens in begining of the traffic shaper script: + tc qdisc del dev eth0 root + tc qdisc add dev eth0 root handle 1: htb default 0x42 + tc class add dev eth0 parent 1: classid 1:1 htb rate 700kbit burst 6k + tc class add dev eth0 parent 1:1 classid 1:42 htb rate 600kbit burst 15k prio 0 + tc qdisc add dev eth0 parent 1:42 handle 42: sfq perturb 20 + tc filter add dev eth0 parent 1: protocol ip prio 1 handle 1 fw RTNETLINK answers: Invalid argument + iptables -t mangle -N to-dsl Any clues?

My previous message (http://mailman.ds9a.nl/pipermail/lartc/2004q2/012285.html) didn''t generate any replies, so I thought I''d try posting what I''ve done trying to solve my own problem, in hopes that someone will take pity and show me if/where I''m going wrong. Just to recap, I''m trying to accomplish this on my server, which streams RealAudio files

...are in use. $TC class add dev $DEV1 parent 1:1 classid 1:20 htb rate 64kbit ceil 856kbit $TC class add dev $DEV1 parent 1:1 classid 1:21 htb rate 64kbit ceil 856kbit $TC class add dev $DEV1 parent 1:1 classid 1:22 htb rate 64kbit ceil 856kbit $TC class add dev $DEV1 parent 1:1 classid 1:37 htb rate 600kbit ceil 856kbit #por defecto $TC class add dev $DEV1 parent 1:1 classid 1:23 htb rate 64kbit ceil 856kbit #oficinas # attach qdisc to leaf classes - here we at SFQ to each priority class. SFQ insures that # within each class connections will be treated (almost)...

...s kbit/sec exept traffic to server: #!/bin/bash TC=/sbin/tc HOSTS_LIST="192.168.1.3 192.168.1.4 192.168.1.5 192.168.1.6 192.168.1. 7 192.168.1.8 192.168.1.9 192.168.1.10 192.168.1.11... DEV=eth0 # ethLAN IMQ=imq0 # --todev 0 NM=17 DN_BANDWIDTH=760Kbit # DN=105Kbit DN_RATE=70Kbit UP_BANDWIDTH=600Kbit # UP=70Kbit UP_RATE=50Kbit $TC qdisc add dev $DEV root handle 1: htb #default 50 $TC class add dev $DEV parent 1: classid 1:1 htb rate ${DN_BANDWIDTH} quantum 1500 iptables -t mangle -N DN_SHAPING ip link set $IMQ up $TC qdisc add dev $IMQ root handle 1: h...

...are in use. $TC class add dev $DEV1 parent 1:1 classid 1:20 htb rate 64kbit ceil 856kbit $TC class add dev $DEV1 parent 1:1 classid 1:21 htb rate 64kbit ceil 856kbit $TC class add dev $DEV1 parent 1:1 classid 1:22 htb rate 64kbit ceil 856kbit $TC class add dev $DEV1 parent 1:1 classid 1:37 htb rate 600kbit ceil 856kbit #por defecto $TC class add dev $DEV1 parent 1:1 classid 1:23 htb rate 64kbit ceil 856kbit #oficinas # attach qdisc to leaf classes - here we at SFQ to each priority class. SFQ insures that # within each class connections will be treated (almost) fair...

...f [ "$1" == "del" ]; then tc qdisc del dev eth0 root handle 1: htb default 10 exit fi tc qdisc add dev eth0 root handle 1: htb default 10 tc class add dev eth0 parent 1: classid 1:1 htb rate 800kbit ceil 900kbit tc class add dev eth0 parent 1:1 classid 1:10 htb rate 300kbit ceil 600kbit tc class add dev eth0 parent 1:1 classid 1:11 htb rate 100kbit ceil 800kbit tc qdisc add dev eth0 parent 1:11 handle 11: pfifo limit 5 tc filter add dev eth0 parent 1:11 protocol ip prio 1 u32 match ip dport 80 0xffff flowid 1:11 unfortunaly when I start that scripts tc filter don''t match...

Hello, I started off by reading the Linux Advanced Routing & Traffic Control Howto, then searched a bit around the web. I see many documents discussing these matters with kernel 2.2.x but they are quite old, something around 1998-2000. I have some questions but I might as well start by exposing my setup to clarify things. I have a couple of internet links: a leased line of 256kbit/s and an