similar to: Deleting ingress tbf

Hi all I''m new to this list, but not exactly to iproute stuff. I''d like to solve a specific problem with bandwidth coming from different external sources towards the internal network (also the other way around, but I figure that''s not so much a problem, since that is egress traffic shaping). The network looks like this: internet ------ ISP-------[shaping/router]

Hello all, My company is sharing it''s internet access with a neighbor and the neighbor in question was eating our bandwidth (both in upload and download) most of the time. I finally set up a linux router to limit the incoming/outgoing bandwidth to his network by adding a tbf on eth0 interface and eth1 interface of the router (neighbor is behind eth1 and we are in-between him and the

ingress can be used to control the incoming packet, such as: tc qdisc add dev eth0 handle ffff: ingress tc filter add dev eth0 parent ffff: protocol ip prio 5 u32 match ip src 172.16.1.11 police rate 10kbit burst 10k drop flowid :1 tc filter add dev eth0 parent ffff: protocol ip prio 5 u32 match ip src 172.16.1.22 police rate 10kbit burst 10k drop flowid :2 first ,I do not sure these method can

Probably this is an old question, but i''m not able to find nothing about... So, i''ve just started to play with tc to limit the transfer speed to my hdsl connection. I''m using the tbf and the command # tc qdisc add dev eth0 root tbf rate 10kbit latency 50ms burst 1000 Then i''ve tried to transfer a big (20 Mbyte) file onto my lan, using ftp and the client

The manual says (about prio): > Because it doesn''t actually shape, the same warning as for SFQ holds: > either use it only if your physical link is really full or wrap it > inside a classful qdisc that does shape. The latter holds for almost all > cable modems and DSL devices. I want to wrap prio inside of tbf. Here''s why: I have a server on a DSL line, which has

Hello , I am trying to install an ingress qdisc on a slackware 7 , 2.2.20 box . I have installed iproute2-2.4.7-now-ss010824.tar.gz . I `ve built all the QOS stuff in my kernel . Playing with cbq sfq etc works ok . However when i try to setup ingress i get the infamous RNETLINK message tc qdisc add dev eth0 handle ffff: ingress RTNETLINK answers: No such file or directory Something weird ,

I''m trying to fill a token bucket with enough tokens to burst several gigs of data. However, it doesn''t seem to get any higher than ~3.9GB: >tc qdisc add dev eth0 root tbf rate 1440kbit latency 50ms \ burst 16000000000 >tc qdisc show dev eth0 qdisc tbf 800b: rate 1440Kbit burst 3908420240b lat 2197.8s A smaller attempt of ~1.6 gigs works just fine: >tc qdisc

I presently use TBF with this syntax: tc qdisc add dev eth0 parent 1:100 tbf buffer=15000/8 LIMIT=30000 MTU=1500 parent class is a cbq with rate=128Kbit when I want to add PEAK, I get always RTNETLINK error: Invalid argument. Maybe be I don''t understand this parameter. What I know about it, it''s that it can control short-term burst traffic, and it''s what I need to do.

Hi, I would like to know how to specify the token rate when a tbf qdic is created using tc tool.. Will it be a default value when tbf qdisc is created? This could be a silly question.... im quite new to all these stuff.. but im really interested.. any help will be most appreciated... thanks in advance, sanjeev -- ______________________________________________ Check out the latest SMS

Hi, I am trying to do both ingress and egress bandwidth management on a bridge. eth0 is the WAN interface. IPTraf shows that the following script is running successfully and it limits bandwidth both ways to 256 KB However when I want to see the statistics using tc - it only shows me stats for htb class and not for ingress class. The tc output is as follows: tc -s -d class show dev eth0 class

Hi Guys, Here is a question that is probably of concern to many of us. I am under pressure to provide some solution for ingress traffic shaping. What my customer demands is to divide the downstream (ingress) of an ADSL lines to two classes of traffic - important traffic and non important downloads. He has a very reasonable requirement: he wants a guarantee of at least 1000kbps at all times for

I''m trying to set up a traffic control on ingress attaching a egress qdisc to the ifb device. The idea is to use a RED algorithm instead of policing the incoming traffic. After trying with tc-red and not obtaining the expected results, I decided to try with something easier, and use htb as bottleneck: ifconfig ifb0 up tc qdisc del dev $dev ingress tc qdisc del dev ifb0 root tc qdisc add

This is my first attempt at understanding lartc: I want to throttle outgoing bandwidth fo a certain tcp port and leave other traffic the way it was. so I put a prio qdisc at the root of eth0 (dummy priomap since i want to use filters to switch bands): $ tc qdisc add dev eth0 root handle 1: prio bands 2 priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 then attach a tbf qdisc at 1:2 : $ tc qdisc add dev

Hi all! I''m new to this list, and hope for some clarity in this matter: I have a home-gateway with linux-2.6.9 and iproute2 (ver:2.6.9). My following tc syntaxes. # eth0 internet scheduleing are: tc qdisc add dev eth0 root handle 1: htb default 20 tc class add dev eth0 parent 1: classid 1:1 htb rate 512kbit burst 6k tc class add dev eth0 parent 1:1 classid 1:10 htb rate 512kbit burst

I''m trying to do some very simple rate-shaping on an interface. I want to limit my 100baseT interface to 7 megs both ingress and egress of the interface. I''ve been hacking my way through the documentation and some examples and I''ve come up with the following configuration for tcng that seems to do what I want. I''m curious if some of the other experts out

Hullo :) I appear to be having a common problem, but the standard fix hasn''t worked for me :/ I''m using a 2.4.23 kernel, with QoS options thusly: # QoS and/or fair queueing # CONFIG_NET_SCHED=y # CONFIG_NET_SCH_CBQ is not set CONFIG_NET_SCH_HTB=m # CONFIG_NET_SCH_CSZ is not set CONFIG_NET_SCH_PRIO=m CONFIG_NET_SCH_RED=m CONFIG_NET_SCH_SFQ=m CONFIG_NET_SCH_TEQL=m

Hi Folks, I''m using a 2.4.x kernel and TC from the iproute2 package so that I can limit traffic through my gateway. I''m using this to mark packets when they leave the LAN: /sbin/ipchains -A forward -j MASQ -i eth0 -s 192.168.1.0/24 -d 0.0.0.0/0 -m 1 When the packets return, I need to have them marked again so that the ingress filter will limit the bandwidth in the opposite

I tried installing the WonderShaper on my internal link, mostly to get the SFQ installed. I set uplink and downlink to 100000 to match the link speed and changed the bandwidth on the cbq line to 100mbit. This killed transfer speed *to* the box, knocking it from 30-40 Mbps down to about 800 kbps. Commenting out just the ingress control restored the speed. What about the ingress policer would do

Hi i have found a problem related with tbf and the latency that the tbf calculates.. I have used the following parameters for burst and limit burst 100Kbit limit 500Kbit lat81.8ms burst 6Kbit limit 6Kbit lat 0us burst 200Kbit limit 100Kbit lat 4294.9s As u can see in the 3rd column the latency for 100Kbit burst and 500Kbit limit is 81.8ms but for 200Kbit and limit 100Kbit is 4294.9s!!! How

Hi, Can you please explain to me the difference between rate and peakrate, in conjucture to TBF. IMHO, rate : controls the no. of pkts flowing through the pipe, and peakrate : controls the no. of tokens flowing through the bucket. A funtion(?) of peakrate and mtu is rate. If this is true, why do I need to specify both peakrate and rate? Regards, suraj. __________________________________ Do