[Solved] Getting bad bufferbloat, SQM only makes it WORSE - reverted to stock firmware

Installing and Using OpenWrt
34

about direction:

Upload and download direction is opposite when you look from WAN interface vs LAN (or WLAN) interface.

Is your old router a dual band n router? You can consider buying a ath9k/mwl8k/ath10k lede compatible 2nd hand router off ebay to extend your wifi network. I got some for under $25 shipped and they are incredibly useful.

In some place I just drop a pair of them down to extend a wireless network using 5ghz band as backhaul and was able to get 140mbps+ throughput with low latency (from the router that act as a client).

35

I'm not sure what cheap router I have. Let me go find it.

EDIT: It is a "TP-Link 300Mbps Wireless Router" (according to the back).

36

The test result doesn't make much sense to me.

Can you post /etc/config/sqm along with the speedtest picture?

Also, to absolutely make sure sqm is initialized properly you can do

/etc/init.d/sqm stop
/etc/init.d/sqm restart

37

Ignore that test. I forgot to save with LuCl. Running again.

UPDATE: Ran it again. Still not perfect bufferbloat elimination, this time the highest being +100ms, but averaging at around +30 or +40ms.

5

38

Are you testing while other devices are using the internet?

The reason I am asking is because I saw some dips from your previous speedtest pictures.

On the other hand, you can continue to tweak the numbers (download and upload) to reduce bufferbloat.

39

Yes, other devices are using the internet, but I'm sadly not in a position where I can control that. As for tweaking the numbers, how would I do that? As in, how would I know whether to increase or decrease each number?

40

You can look at the detailed result of the speedtest, and check latency for download and upload.

If the latency is high for download, then adjust the number "option download" downward until you get a good latency.

41

It seems to be entirely dependent on what other people in my house are doing. I overheard someone watching a YouTube video at the last test, but this test bufferbloat was almost perfect (+30ms at most), with an A+ in quality.

Not sure how the router fits into this by the way. Can you elaborate?

42

I'm about to do a wireless test with the current settings. Stand by.

As expected, the wireless test gives the same results EXCEPT for the incredibly terrible bufferbloat.

43

Hi @Kampfkarren,
unfortunately this configuration does not work at all, for a number of reasons.

  1. piece_of_cake.qos requires the cake qdisc, but the fact that it is not reported as in use in the tc-s qdsisc output seems to indicate that it is not installed, in that case you will have a non-working configuration, but there should be an error reported in the output of logread...

  2. br-wan is an internally facing (bridged) interface and for those the direction of the shaper is flipped in relation to the direction in relation to the internet. Shapers are configured for the ingress and egress direction of specific interfaces and the "downloading" text in the GUI is short hand for interface ingress while upload is shorthand for interface egress (in the typical use-case, sqm instantiated on the internet facing interface these two definitions if directionality align and interface ingress equals internet download).
    Tl; dr: On internally facing interfaces configure the internet upload in the download GUI-field and internet download in the upload GUI-field. (This is actually documented in the notes and the faq section of https://lede-project.org/docs/user-guide/sqm)

Best Regards

44

Ah, I see you fixed that issue already.

I would recommend to read https://lede-project.org/docs/user-guide/sqm now and try the recommendations in the "sing and dance section" as well as try to configure the appropriate overhead.

BUT please do the following first:

  1. "cat /etc/config/sqm"

  2. "ifstatus wan"

  3. "SQM_DEBUG=1 SQM_VERBOSITY_MAX=8 /etc/init.d/sqm stop ; SQM_DEBUG=1 SQM_VERBOSITY_MAX=8 /etc/init.d/sqm start"

  4. "logread | grep SQM"

  5. "cat /var/run/sqm/*debug.log"

  6. "tc -s qdisc"
    Then run a dsl reports speedtest.

  7. tc -s qdisc

and please post the output of all of the CLI commands; that should give clearer inside into what actually happens.

Final question, is the lede router the only device connected to the DOCSIS modem, or are you also

45 
root@LEDE:~# cat /etc/config/sqm

config queue 'eth1'
        option qdisc_advanced '0'
        option linklayer 'none'
        option enabled '1'
        option debug_logging '0'
        option verbosity '5'
        option script 'piece_of_cake.qos'
        option interface 'eth1'
        option qdisc 'cake'
        option download '62000'
        option upload '4500'

root@LEDE:~# ifstatus wan
{
        "up": true,
        "pending": false,
        "available": true,
        "autostart": true,
        "dynamic": false,
        "uptime": 283500,
        "l3_device": "br-wan",
        "proto": "dhcp",
        "device": "br-wan",
        "metric": 0,
        "dns_metric": 0,
        "delegation": true,
        "ipv4-address": [
                {
                        "address": "174.81.15.112",
                        "mask": 22
                }
        ],
        "ipv6-address": [

        ],
        "ipv6-prefix": [

        ],
        "ipv6-prefix-assignment": [

        ],
        "route": [
                {
                        "target": "174.81.12.1",
                        "mask": 32,
                        "nexthop": "0.0.0.0",
                        "source": "174.81.15.112\/32"
                },
                {
                        "target": "0.0.0.0",
                        "mask": 0,
                        "nexthop": "174.81.12.1",
                        "source": "174.81.15.112\/32"
                }
        ],
        "dns-server": [
                "71.10.216.1",
                "71.10.216.2"
        ],
        "dns-search": [
                "charter.com"
        ],
        "inactive": {
                "ipv4-address": [

                ],
                "ipv6-address": [

                ],
                "route": [

                ],
                "dns-server": [

                ],
                "dns-search": [

                ]
        },
        "data": {
                "leasetime": 28800
        }
}
root@LEDE:~# SQM_DEBUG=1 SQM_VERBOSITY_MAX=8 /etc/init.d/sqm stop ; SQM_DEBUG=1 SQM_VERBOSITY_MAX=8 /etc/init.d/sqm start
SQM: Starting SQM script: piece_of_cake.qos on eth1, in: 62000 Kbps, out: 4500 Kbps
SQM: QDISC cake is useable.
SQM: Starting piece_of_cake.qos
SQM: ifb associated with interface eth1: 
SQM: Currently no ifb is associated with eth1, this is normal during starting of the sqm system.
SQM: egress
SQM: egress shaping activated
SQM: QDISC ingress is useable.
SQM: ingress
SQM: ingress shaping activated
SQM: piece_of_cake.qos was started on eth1 successfully
root@LEDE:~# logread | grep SQM
Tue Jan  9 14:22:16 2018 user.notice SQM: Starting SQM script: piece_of_cake.qos on eth1, in: 62000 Kbps, out: 4500 Kbps
Tue Jan  9 14:22:16 2018 user.notice SQM: QDISC cake is useable.
Tue Jan  9 14:22:16 2018 user.notice SQM: Starting piece_of_cake.qos
Tue Jan  9 14:22:16 2018 user.notice SQM: ifb associated with interface eth1: 
Tue Jan  9 14:22:16 2018 user.notice SQM: Currently no ifb is associated with eth1, this is normal during starting of the sqm system.
Tue Jan  9 14:22:16 2018 user.notice SQM: egress
Tue Jan  9 14:22:16 2018 user.notice SQM: egress shaping activated
Tue Jan  9 14:22:16 2018 user.notice SQM: QDISC ingress is useable.
Tue Jan  9 14:22:16 2018 user.notice SQM: ingress
Tue Jan  9 14:22:16 2018 user.notice SQM: ingress shaping activated
Tue Jan  9 14:22:16 2018 user.notice SQM: piece_of_cake.qos was started on eth1 successfully
root@LEDE:~# cat /var/run/sqm/*debug.log

Tue Jan  9 14:22:16 UTC 2018: Starting.
Starting SQM script: piece_of_cake.qos on eth1, in: 62000 Kbps, out: 4500 Kbps
Failed to find act_ipt. Maybe it is a built in module ?
module is already loaded - sch_cake
module is already loaded - sch_ingress
module is already loaded - act_mirred
module is already loaded - cls_fw
module is already loaded - cls_flow
module is already loaded - cls_u32
module is already loaded - sch_htb
module is already loaded - sch_hfsc
/sbin/ip link add name TMP_IFB_4_SQM type ifb
/usr/sbin/tc qdisc replace dev TMP_IFB_4_SQM root cake
QDISC cake is useable.
/sbin/ip link set dev TMP_IFB_4_SQM down
/sbin/ip link delete TMP_IFB_4_SQM type ifb
Starting piece_of_cake.qos
/usr/sbin/tc -p filter show parent ffff: dev eth1
ifb associated with interface eth1: 
/usr/sbin/tc -p filter show parent ffff: dev eth1
Currently no ifb is associated with eth1, this is normal during starting of the sqm system.
/sbin/ip link add name ifb4eth1 type ifb
egress
/usr/sbin/tc qdisc del dev eth1 root
RTNETLINK answers: No such file or directory
/usr/sbin/tc qdisc add dev eth1 root cake bandwidth 4500kbit besteffort
egress shaping activated
/sbin/ip link add name TMP_IFB_4_SQM type ifb
/usr/sbin/tc qdisc replace dev TMP_IFB_4_SQM ingress
QDISC ingress is useable.
/sbin/ip link set dev TMP_IFB_4_SQM down
/sbin/ip link delete TMP_IFB_4_SQM type ifb
ingress
/usr/sbin/tc qdisc del dev eth1 handle ffff: ingress
RTNETLINK answers: Invalid argument
/usr/sbin/tc qdisc add dev eth1 handle ffff: ingress
/usr/sbin/tc qdisc del dev ifb4eth1 root
RTNETLINK answers: No such file or directory
/usr/sbin/tc qdisc add dev ifb4eth1 root cake bandwidth 62000kbit besteffort wash
/sbin/ip link set dev ifb4eth1 up
/usr/sbin/tc filter add dev eth1 parent ffff: protocol all prio 10 u32 match u32 0 0 flowid 1:1 action mirred egress redirect dev ifb4eth1
ingress shaping activated
piece_of_cake.qos was started on eth1 successfully
root@LEDE:~# 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 mq 0: dev eth0 root 
 Sent 751251352 bytes 724296 pkt (dropped 0, overlimits 0 requeues 19) 
 backlog 0b 0p requeues 19 
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 751251352 bytes 724296 pkt (dropped 0, overlimits 0 requeues 19) 
 backlog 0b 0p requeues 19 
  maxpacket 3028 drop_overlimit 0 new_flow_count 671 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :5 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :6 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :7 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :8 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc cake 801f: dev eth1 root refcnt 9 bandwidth 4500Kbit besteffort triple-isolate rtt 100.0ms raw total_overhead 14 hard_header_len 14 
 Sent 45386 bytes 272 pkt (dropped 0, overlimits 76 requeues 0) 
 backlog 0b 0p requeues 0 
 memory used: 50304b of 4Mb
 capacity estimate: 4500Kbit
                  Tin 0
  thresh       4500Kbit
  target          5.0ms
  interval      100.0ms
  pk_delay        1.5ms
  av_delay         70us
  sp_delay          1us
  pkts              272
  bytes           45386
  way_inds            0
  way_miss           49
  way_cols            0
  drops               0
  marks               0
  sp_flows            0
  bk_flows            1
  un_flows            0
  max_len          1514

qdisc ingress ffff: dev eth1 parent ffff:fff1 ---------------- 
 Sent 67986 bytes 265 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 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 br-wan root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc noqueue 0: dev br-wan6 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc mq 0: dev wlan1 root 
 Sent 92955104481 bytes 70268205 pkt (dropped 2714, overlimits 0 requeues 866) 
 backlog 0b 0p requeues 866 
qdisc fq_codel 0: dev wlan1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 1149380 bytes 7893 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 86 drop_overlimit 0 new_flow_count 1 ecn_mark 0
  new_flows_len 1 old_flows_len 0
qdisc fq_codel 0: dev wlan1 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 193093252 bytes 145841 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan1 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 92760861849 bytes 70114471 pkt (dropped 2714, overlimits 0 requeues 866) 
 backlog 0b 0p requeues 866 
  maxpacket 16346 drop_overlimit 192 new_flow_count 241098 ecn_mark 2
  new_flows_len 1 old_flows_len 0
qdisc fq_codel 0: dev wlan1 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc mq 0: dev wlan0 root 
 Sent 188163438 bytes 288237 pkt (dropped 0, overlimits 0 requeues 1) 
 backlog 0b 0p requeues 1 
qdisc fq_codel 0: dev wlan0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 14828 bytes 72 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan0 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan0 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 188148610 bytes 288165 pkt (dropped 0, overlimits 0 requeues 1) 
 backlog 0b 0p requeues 1 
  maxpacket 4542 drop_overlimit 0 new_flow_count 1658 ecn_mark 0
  new_flows_len 1 old_flows_len 0
qdisc fq_codel 0: dev wlan0 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc cake 8020: dev ifb4eth1 root refcnt 2 bandwidth 62Mbit besteffort triple-isolate wash rtt 100.0ms raw total_overhead 14 hard_header_len 14 
 Sent 71956 bytes 265 pkt (dropped 0, overlimits 41 requeues 0) 
 backlog 0b 0p requeues 0 
 memory used: 3466b of 4Mb
 capacity estimate: 62Mbit
                  Tin 0
  thresh         62Mbit
  target          5.0ms
  interval      100.0ms
  pk_delay        116us
  av_delay          5us
  sp_delay          2us
  pkts              265
  bytes           71956
  way_inds            0
  way_miss           55
  way_cols            0
  drops               0
  marks               0
  sp_flows            0
  bk_flows            1
  un_flows            0
  max_len          2102

root@LEDE:~# echo did speed test (was wireless)
-ash: syntax error: unexpected "("
root@LEDE:~# 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 mq 0: dev eth0 root 
 Sent 751272224 bytes 724402 pkt (dropped 0, overlimits 0 requeues 19) 
 backlog 0b 0p requeues 19 
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 751272224 bytes 724402 pkt (dropped 0, overlimits 0 requeues 19) 
 backlog 0b 0p requeues 19 
  maxpacket 3028 drop_overlimit 0 new_flow_count 671 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :5 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :6 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :7 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :8 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc cake 801f: dev eth1 root refcnt 9 bandwidth 4500Kbit besteffort triple-isolate rtt 100.0ms raw total_overhead 14 hard_header_len 14 
 Sent 11877003 bytes 22300 pkt (dropped 625, overlimits 41120 requeues 0) 
 backlog 0b 0p requeues 0 
 memory used: 2800256b of 4Mb
 capacity estimate: 4500Kbit
                  Tin 0
  thresh       4500Kbit
  target          5.0ms
  interval      100.0ms
  pk_delay       10.9ms
  av_delay        5.7ms
  sp_delay          3us
  pkts            22925
  bytes        12801125
  way_inds            0
  way_miss          324
  way_cols            0
  drops             625
  marks               0
  sp_flows            0
  bk_flows            1
  un_flows            0
  max_len          1514

qdisc ingress ffff: dev eth1 parent ffff:fff1 ---------------- 
 Sent 29705751 bytes 27745 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 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 br-wan root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc noqueue 0: dev br-wan6 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
qdisc mq 0: dev wlan1 root 
 Sent 92985192211 bytes 70295818 pkt (dropped 2801, overlimits 0 requeues 867) 
 backlog 0b 0p requeues 867 
qdisc fq_codel 0: dev wlan1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 1150120 bytes 7903 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 86 drop_overlimit 0 new_flow_count 1 ecn_mark 0
  new_flows_len 1 old_flows_len 0
qdisc fq_codel 0: dev wlan1 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 193093252 bytes 145841 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan1 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 92790948839 bytes 70142074 pkt (dropped 2801, overlimits 0 requeues 867) 
 backlog 0b 0p requeues 867 
  maxpacket 16346 drop_overlimit 192 new_flow_count 241191 ecn_mark 2
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan1 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc mq 0: dev wlan0 root 
 Sent 188184310 bytes 288343 pkt (dropped 0, overlimits 0 requeues 1) 
 backlog 0b 0p requeues 1 
qdisc fq_codel 0: dev wlan0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 14828 bytes 72 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan0 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan0 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 188169482 bytes 288271 pkt (dropped 0, overlimits 0 requeues 1) 
 backlog 0b 0p requeues 1 
  maxpacket 4542 drop_overlimit 0 new_flow_count 1659 ecn_mark 0
  new_flows_len 1 old_flows_len 0
qdisc fq_codel 0: dev wlan0 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc cake 8020: dev ifb4eth1 root refcnt 2 bandwidth 62Mbit besteffort triple-isolate wash rtt 100.0ms raw total_overhead 14 hard_header_len 14 
 Sent 30237307 bytes 27732 pkt (dropped 13, overlimits 29890 requeues 0) 
 backlog 0b 0p requeues 0 
 memory used: 206576b of 4Mb
 capacity estimate: 62Mbit
                  Tin 0
  thresh         62Mbit
  target          5.0ms
  interval      100.0ms
  pk_delay        224us
  av_delay         12us
  sp_delay          1us
  pkts            27745
  bytes        30256989
  way_inds            0
  way_miss          351
  way_cols            0
  drops              13
  marks               0
  sp_flows            0
  bk_flows            1
  un_flows            0
  max_len          7570

The LEDE router is the only device connected to my modem.

46

This is odd, what the heck is br-wan (why a bridge)? But if eth1 works and the directionality is correct in regards to the internet, then it is clear that eth1 is carrying the wan traffic... so ignore my puzzlement.

The rest all looks okay. The next step would be to add proper overhead accounting, in your case you need to specify 18 bytes of per packet overhead (ethernet with overhead).

here is the /etc/config/sqm I would try:

    option debug_logging '0'
    option verbosity '5'
    option interface 'eth1'
    option download '62000'
    option upload '4500'
    option qdisc 'cake'
    option script 'piece_of_cake.qos'
    option qdisc_advanced '1'
    option squash_dscp '0'
    option squash_ingress '0'
    option ingress_ecn 'ECN'
    option egress_ecn 'ECN'
    option qdisc_really_really_advanced '1'
    option iqdisc_opts 'nat dual-dsthost ingress mpu 64'
    option eqdisc_opts 'nat dual-srchost mpu 64'
    option linklayer 'ethernet'
    option overhead '18'
    option linklayer_advanced '1'
    option tcMTU '2047'
    option tcTSIZE '128'
    option tcMPU '64'
    option linklayer_adaptation_mechanism 'cake'
    option enabled '1'

This (the "nat dual-XXXhost" keywords) will try to fairly share the available bandwidth between all concurrently active hosts (well IP-addresses) which for many home situations seems to be a pretty nice and predictable, heuristic. The "ingress" keyword will make the ingress shaper try to shape its incoming side instead of the typical outgoing side, this will cost some bandwidth, but should work better with higher numbers of incoming flows (this is still experimental).

I believe the sch_cake and tc in the 17.01 repository should already be updated to versions supporting these keywords.

Best Regards

47

On option dual-dsthost/dual-srchost - I've found that the default triple isolation for individual connection generally works better in fighting bufferbloat. The drawback being that you don't get bandwidth faireness across host, but rather fairness across individual connection i.e. whoever has most connections has advantage in getting more bandwidth.

While dual-dsthost/dual-srchost settings seems to split bandwidth fairly across hosts but I've found that if I simultaneously run one throughput demanding application and one latency sensitive application on the same host, bufferbloat issue resurface (running throughput demanding application on a different host, however, does not cause latency issue on the latency sensitive application.)

Do you know if there's a way to ensure fairness for streams/connections within the same host?

48

This is the wireless speed test I get with that config.

Selection_076

Note that my config right now is on "eth1". Would this mean that my config doesn't effect me at all if I'm wireless?

49

No you should be setting up sqm on the interface that is physically connected to your cable modem, this then prevents bufferbloat in the modem or other ISP equipment by managing the flow in your router instead.

50

Is your cable modem in bridge mode? (WiFi turned off, DHCP off).

51

No. WiFi is absolutely on.

52

WiFi and DHCP should be off on the cable modem.

It's now the router's job.

53

I misread, I thought you asked if the router had WiFi. I have no idea how to check or change those settings on my modem.