It brings up a good point though, which is that when it comes to explicit prioritization, there can never be a one-size-fits-all scenario. Business offices with tens or hundreds of VoIP phones will be different from gamers at home who don't use VoIP at all. Guest networks will be different from "main" networks. IoT devices will be different from desktops under your complete control... It's all about achieving high "utility" which is inherently an individualized concept. Cake does a great job because many people just want "everything to be not too delayed". But the call center company with 200 VoIP phones might well want to delay the off duty employees surfing Facebook by quite a lot
Yes thanks for pointing it out. And yes, I was kinda suspicious of dslreports pings. I'm confident that my code above fits pretty well with my personal requirements, but anyone doing DSCP tagging should think out their own requirements rather than copy and paste.
EDIT: Also I've taken to tagging everything CS2 by default. It works better with low end switches such as TP-Link which tend to assume they can treat DSCP as a monotone increasing priority number. Most people treat CS0 and CS1 correctly, but these low end switches will actually prioritize the CS1 scavenging traffic over the normal traffic. So I just bump all CS0 to CS2 as it transits the router inbound.