Re: [Cerowrt-devel] Turris Omnia

[James Cloos <cloos@jhcloos.com>]

I don't know why I didn't think of this last night, but I prevented
wshaper from starting at boot and rebooted, and now throughput is
reasonable.

luci/admin/status/overview still reports inaccurate values, but someone
on linux-wireless explained that the ath10 hw chooses the tx internally
and apparently doesn't report it, so that is expected.

But I was able to transfer to the client device at around 300 Mbps now,
with wshaper not started.

tc q still reports that fq_codel is in use:

qdisc mq 0: dev wlan1 root 
qdisc fq_codel 0: dev wlan1 parent :1 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan1 parent :2 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan1 parent :3 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan1 parent :4 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc mq 0: dev wlan0 root 
qdisc fq_codel 0: dev wlan0 parent :1 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan0 parent :2 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan0 parent :3 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan0 parent :4 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 

but with wshaper there were 8 rather than 4 lines matching parent for
each interface.  There still are 8 for the 3 ethernet devices, but that
doesn't seem to be a problem....

So this seems solved.

Thanks.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6