Hi Jonathan

Thanks for your quick answer. REally appreciate it!!!

I wil try later the cake statement (is it the same as codel)?. I am starting with Codel. So I need to have a better understanding of codel.

I have the following scenario

Where client asks for a FTP file to server. Link between router-server has a 150MBit speed with a delay of 250 ms.

Then link between client and router has 10 Mbit and the Codel algorithm. So I am checking the differences between having codel or not.

Do you have an advice to have a good scenario for testing Codel properly? Or a document to know how the differences parameter can affect to the communication?

In my scenario it seems it is better not having Codel. See attached ClientFTPCodelNO-NO-NO (nocodel) versus ClientFtpCodel1000..

where a Codel Algorithm of 1000 packets, 13 ms target and 100 interval is configured

Regards.

El lun., 14 ene. 2019 a las 16:24, Jonathan Morton (<chromatix99@gmail.com>) escribió:

> On 14 Jan, 2019, at 12:54 pm, Rodrigo Alvarez Dominguez <rodroleon@gmail.com> wrote:
>
> I would like to know if it is possible to have the following configuration where there is a rate limit and codel algorithm configured over the same interface
>
> tc qdisc add dev r1-eth0 root handle 1: htb
> tc class add dev r1-eth0 parent 1: classid 1:1 htb rate 10000kbit burst 15kbit
> tc qdisc add dev r1-eth0 parent 1:1 handle 10: fq_codel limit 1000 target 5000 interval 10000 noecn
> tc filter add dev r1-eth0 protocol ip prio 1 u32 match ip dst 0.0.0.0/0 flowid 1:1

Yes, this is an extensively tested configuration. Have you tried it?

You could also just use Cake, which does all the above, better, with only one tc invocation:

tc qdisc replace dev r1-eth0 root handle 1: cake bandwidth 10000kbit besteffort flows

- Jonathan Morton