GGounot wrote:
The diagram is : Internet <=> eth0 <=> eth1 <=> Client computer (which downloads using Firefox) So shaping on eth1 outgoing traffic should limit the rate Client receives data from Internet. Would shaping on eth0 using : tc qdisc add dev eth0handle ffff: ingress ifconfig ifb0 up tc filter add dev eth0 parent ffff: protocol all u32 match u32 0 0 action mirred egress redirect dev ifb0 and run the script on ifb0 be a better solution ?
You could but don't need to as you can do it on eth1. Which ever way you are going to be shaping from the wrong end of the bottleneck so will need to sacrifice some bandwidth for it to work. My previous answer 2. was a bit misleading as it would only have applied if you were maxing eth speed.
Other way : eth0 has a public IP (is directly connected to Internet). eth0 and eth1 are 100Mb/s network PCI cards. The Internet link has a rate of ~4000Kb/s. Is the use of PRIO qdisc the problem ? (since it (maybe) acts on the network card rate, not the actual Internet connection rate)
Yes, prio is the problem you need to send the traffic from the internet to something like htb with the rate set to eg. 3500kbit then you can use htb classes to give prio for some traffic over other. You could if you wanted use prio qdisc as a child of htb. -- To unsubscribe from this list: send the line "unsubscribe lartc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
