diff options
| author | Viacheslav Hletenko <v.gletenko@vyos.io> | 2023-06-16 13:29:41 +0000 |
|---|---|---|
| committer | Viacheslav Hletenko <v.gletenko@vyos.io> | 2023-06-16 13:38:26 +0000 |
| commit | 08b333eac3c274a9111e68823e5c9de585add5e4 (patch) | |
| tree | 97a2d82d228e5b4fc0b0d7633d85afe0971994a5 /src/op_mode/monitor_bandwidth_test.sh | |
| parent | c67c51e0202d9eafed6a719a49dd6885132c76ec (diff) | |
| download | vyos-1x-08b333eac3c274a9111e68823e5c9de585add5e4.tar.gz vyos-1x-08b333eac3c274a9111e68823e5c9de585add5e4.zip | |
T5295: Fix QoS shaper rate limit
Do not handle rate via 'tc filter' directly but rather set the
'tc filter' to direct traffic to the correct tc class flow.
As it in 1.3.
It fixes random unexpected shapes, when you set for example 300mbit
but get 3-11mbit
Current implementation seems not correct as it uses rate limits
two times (in class and in filter):
tc class replace dev eth0 parent 1:1 classid 1:17 htb rate 250000000 \
burst 15k quantum 1514
tc filter replace dev eth0 parent 1: protocol all u32 match \
ip dst 192.168.122.11 action police rate 250000000 burst 15k flowid 1:17
The correct way after fix:
tc class replace dev eth0 parent 1:1 classid 1:17 htb rate 250000000 \
burst 15k quantum 1514
tc filter replace dev eth0 parent 1: protocol all u32 match \
ip dst 192.168.122.11 flowid 1:17
Diffstat (limited to 'src/op_mode/monitor_bandwidth_test.sh')
0 files changed, 0 insertions, 0 deletions