search for: 220kbit

Hi all, Im new to all this, and am still trying to get my head qround some of the concepts of how this all works. Ive read the howto''s, man pages etc. Ive setup packet shaping on my router/server box using HTB and SFQ, but its not working the way i would like. Im after shaping that has "weights" for classes so that a lower priority class will slow down when a higher class

Hello, I was attempting to throttle egress traffic to a specific rate using a tbf. As a starting point I used an example from the LARTC howto, which goes: tc qdisc add dev eth1 root tbf rate 220kbit latency 50ms burst 1540 I then attempt a large fetch from another machine via wget (~40 megs) and the rate was clamped down to about 12Kbytes/s. As this seemed too much, I gradually increased the latency up to 200ms which then gave me the expected results (~34Kbytes/s). I then applied this qu...

...udp traffic(generated by the VoIP applications) to 1:110. I continously generate ping traffic on the computer and the router to a remote computer in the ISP network. The pings from the computer are classified as 1:105, while the pings from the router are classified as 1:800. The max uplink speed is 220Kbit determined by observation. In the first test, I limit the SUBCLASS_OUTRATE to 200Kbit. Both pings are around 20ms before I start the VoIP services. However, once I start the services, the pings jump up to 1800ms. In the second test, I limit the SUBCLASS_OUTRATE to 180Kbit. The pings jump up to 80...

Hi All, I read the advanced networking howto and find a useful way to shape my adsl link. is says: "tc qdisc add dev ppp0 root tbf rate 220kbit latency 50ms burst 1500 [...] Change 220kbit to your uplinks *actual* speed, minus a few percent. If you have a really fast modem, raise ''burst'' a bit. " My adsl''s upload brandwidth is about 120 kbits/sec, download brandwidth is about 384 kbits/sec. So I use tc...

Hi, I am a completely newbie, and have been doing intense reading for the entire last week, and have the following novice question: In section 9.2.2.2. of LARTC HOWTO, the following sample configuration given: # tc qdisc add dev ppp0 root tbf rate 220kbit latency 50ms burst 1540 Why is the burst parameter value determined to be 1540? Thanks, Todd _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

...imit the upload with 100kbit per user. Ex: 192.168.1.20 ----> 1024kbit-DOWN / 100kbit-UP 192.168.1.21 ----> 1024kbit-DOWN / 100kbit-UP and so on....... Ive tried CBQ and HTB, but couldnt get is right. the only thing that I did in upload bases was: "tc qdisc add dev ppp0 root tbf rate 220kbit latency 50ms burst 1540" witch is for the whole interface. not for a simple IP. Thanks a lot. Cristiano Soares

...> /dev/null $TC qdisc del dev ppp0 root 2> /dev/null > /dev/null $IPTABLES -F POSTROUTING -t mangle $TC qdisc add dev eth0 root handle 1: htb default 50 r2q 2 $TC class add dev eth0 parent 1: classid 1:2 htb rate 248Kbit burst 35k $TC class add dev eth0 parent 1:2 classid 1:10 htb rate 220Kbit ceil 240Kbit burst 25k prio 0 $TC class add dev eth0 parent 1:2 classid 1:30 htb rate 28Kbit ceil 28Kbit burst 10k prio 1 $TC qdisc add dev eth0 parent 1:10 handle 11: sfq perturb 10 $TC qdisc add dev eth0 parent 1:30 handle 33: sfq perturb 10 $IPTABLES -t mangle -A POSTROUTING -o eth0 -s ! 192....

...l flows, "p2p" and "!p2p". The entire desktop-to-inet traffic should be constrained to 240kbit/s. If the two flows don''t compete for this 240kbit/s (their combined upload stays below 240kbit/s), then each can use whatever it feels like (for example, "p2p" uses 220kbit/s, "!p2p" uses 10kbit/s). If they do compete, then "p2p" should be constrained to 140kbit/s, and "!p2p" should be constrained to 100kbit/s. For (1), I chose PRIO, for (2), I chose HTB. legend: [qdisc], (class) [1:0 PRIO, 2 bands]...

...dev/null $TC qdisc del dev eth1 ingress 2> /dev/null > /dev/null $IPTABLES -F POSTROUTING -t mangle $TC qdisc add dev eth0 root handle 1: htb default 50 r2q 2 $TC class add dev eth0 parent 1: classid 1:2 htb rate 248Kbit burst 35k $TC class add dev eth0 parent 1:2 classid 1:10 htb rate 220Kbit ceil 240Kbit burst 25k prio 0 $TC class add dev eth0 parent 1:2 classid 1:30 htb rate 28Kbit ceil 28Kbit burst 10k prio 1 $TC class add dev eth0 parent 1: classid 1:60 htb rate 1Kbit ceil 100Mbit prio 1 $TC qdisc add dev eth0 parent 1:10 handle 11: sfq perturb 10 $TC qdisc add dev eth0 parent 1...

Folks, I am a little bit confuse in how to put these packets into correct mangle table for traffic shaping. This is what i ve planned to do: - - - - :eth0 [ LINUX-BOX ] eth1: - - - - Let say: eth0: 220.100.1.1 eth1: 192.168.1.1 eth1:1 192.168.1.2 192.168.1.0/24 get natted into 220.100.1.1 before reaching the internet. I put every packets coming from internet (eth0) this way: # iptables -t