you are making me pull out my mrtg stats, I'll post one. In the
debloating universe, 5 minute averages
really obscure the bufferbloat problem. What's important are
drops/marks, reschedules, queue depths, and overlimits. I get about
3000 drops/day (debloats). I wish I could extrapolate what that and
the reschedules means in terms of induced latency on other flows,
easily.
The reminders are useful, but sorry if those mrtg stats gives you flashbacks to 2001, XP and Napster rips. :)
As I look at different router configs, queue management looks like it’s being applied inconsistently, sometimes on the backhaul interfaces, and most often just on the customer facing interfaces (interfaces connected to the point-to-multipoint APs).
I would only do it on the point-to-point links, as I would think you need airtime fairness and queues per station to do much good on ptmp. Failing that, I would probably just let the APs do what they will(?) That said, the Ethernet interfaces to NSM5s are 100Mbit, and in that case, a qdisc on egress towards the AP makes sense.
SmokePing should be public. On this AP, eth0 is the ptmp radio and eth1 the backhaul, which has pfifo_fast, so yeah, there’s work to do, and quite a few overlimits on at least one hfsc qdisc...