iproute2 package breaks tc classification

[seii]

Hey everyone, just wanted to post about this here. I’m using an EspressoBin as my router, and it appears that upgrading to the current “latest” iproute2 package (4.15.0-1) broke tc’s ability to classify packets. For me, the solution was to roll-back to the previous version (4.14.1-2). No idea why just yet, but you’re welcome to check out this thread [1] to see if there’s ever any follow-up.

[1] https://superuser.com/questions/1299875/what-could-cause-tc-to-stop-classifying-packets

[seii]

I was unable to verify if iproute2 actually broke any functionality in the updated version, but it definitely turned out that iproute2 changed how “tc” displays its output. I am using FireQOS, and the developer was able to patch it to take into account iproute2’s newer format.

[Author]

Posts