I have not done further tests yet but the graphs are empty on all my machines.
I can reproduce this behaviour.
Unfortunately, I need help for this bug, since I could not figure out where collectd will get the information on traffic for different QoS classes from. Any hints are highly appreciated. :-)
collectd is not involved at all. tc triggers some functions that parse the data and update the rrd itself. https://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=config/qos;hb=98d78fa824fd30a9bc2b90f7d3831ff20c9997b4
Thanks. Using /sbin/tc from Core Update 173 causes everything to be fine again, so this limits the area where to look for.
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=ca06e817b84b8bb737b2811bdc5ad43d034e2c48
I would consider this an unintentional change and therefore suggest to change the regular expression that it is going to be happy with either string.
Roger that, will do so.
https://patchwork.ipfire.org/project/ipfire/patch/20230622155115.1741-1-michael.tremer@ipfire.org/ Given that this has been resolved upstream meanwhile, the regular expression change has become redundant.
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=52d0a1e2db1c33b760cf2e59e726dfbc4ad23196
https://blog.ipfire.org/post/ipfire-2-27-core-update-176-is-available-for-testing
Fix of reverting the regex change has been tested out in Bug#13150 and verified. Therefore also making this bug as verified.
Core Update 176 released https://blog.ipfire.org/post/ipfire-2-27-core-update-176-released