Can someone help me explain QoS performance?

root@OpenWrt:~# tc -s qdisc
qdisc noqueue 0: dev lo root refcnt 2
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc fq_codel 0: dev eth0 root refcnt 2 limit 10240p flows 1024 quantum 1514 ta                                                                                               rget 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 1488247799 bytes 2600428 pkt (dropped 0, overlimits 0 requeues 37)
 backlog 0b 0p requeues 37
  maxpacket 3028 drop_overlimit 0 new_flow_count 12838 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc noqueue 0: dev br-lan root refcnt 2
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev eth0.1 root refcnt 2
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc cake 800d: dev eth0.2 root refcnt 2 bandwidth 16Mbit besteffort dual-srcho                                                                                               st nat nowash ack-filter split-gso rtt 100.0ms noatm overhead 8
 Sent 209647870 bytes 1119159 pkt (dropped 90, overlimits 75928 requeues 0)
 backlog 0b 0p requeues 0
 memory used: 241920b of 4Mb
 capacity estimate: 16Mbit
 min/max network layer size:           28 /    1500
 min/max overhead-adjusted size:       36 /    1508
 average network hdr offset:           14

                  Tin 0
  thresh         16Mbit
  target          5.0ms
  interval      100.0ms
  pk_delay       10.0ms
  av_delay        846us
  sp_delay         19us
  backlog            0b
  pkts          1119249
  bytes       209718044
  way_inds        24454
  way_miss        34658
  way_cols            0
  drops              58
  marks               0
  ack_drop           32
  sp_flows            2
  bk_flows            1
  un_flows            0
  max_len          6056
  quantum           488

qdisc ingress ffff: dev eth0.2 parent ffff:fff1 ----------------
 Sent 1220229490 bytes 1396435 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc cake 800e: dev ifb4eth0.2 root refcnt 2 bandwidth 59Mbit besteffort dual-d                                                                                               sthost nat wash ingress no-ack-filter split-gso rtt 100.0ms noatm overhead 8
 Sent 1240292709 bytes 1396099 pkt (dropped 336, overlimits 657107 requeues 0)
 backlog 0b 0p requeues 0
 memory used: 252000b of 4Mb
 capacity estimate: 59Mbit
 min/max network layer size:           46 /    1500
 min/max overhead-adjusted size:       54 /    1508
 average network hdr offset:           14

                  Tin 0
  thresh         59Mbit
  target          5.0ms
  interval      100.0ms
  pk_delay        9.7ms
  av_delay        4.1ms
  sp_delay         10us
  backlog            0b
  pkts          1396435
  bytes      1240727120
  way_inds        30793
  way_miss        28287
  way_cols            0
  drops             336
  marks               0
  ack_drop            0
  sp_flows            4
  bk_flows            1
  un_flows            0
  max_len          6056
  quantum          1514

with my router connected to the box my connexion seem good but my character in video games is very low

@dlakelan

It's working, but there are packet drops. It's normal for cake to drop packets, but generally you want it to drop the right packets, not your game packets. This is part of why cake is general purpose and other scripts I have developed are special purpose for gamers and voip/zoom users etc.

hello dlakelan i'm wait your script finish completly because doesn't work at my home

thanks i'm appreciate your help :slight_smile:

i have a question what the difference between source zone source adress destination zone and detiantion adress

Please go to that thread where we are working on the script and give feedback if it isn't working. I need to know what isn't working to be able to fix it, what is behavior that happens? how do qdisc stats look before and after playing games etc? It won't magically fix itself if I don't know what's wrong!

As for difference between "zone" and "address" the firewall has an idea of zones. They correspond to a set of interfaces: you could have say several LAN ethernet networks all in the same "zone" so they talk to each other no problem, but can't talk to other zones like "WAN" or like "DMZ" or "guest" etc.

2 Likes