Hi all!
Are there any knows problems with Mangling/queueing in 2.9? I have quite a few mangle rules, all of which seem to do their packet/bytes counting correctly.
However, when I try to use these in the queue tree, most of them show no traffic at all, even when the mangle rule counters keep going…
Yes, I’m seeing this as well. Queue counters were working fine yesterday, today, nothing. As you say, the mangle counters are still running.
In addition, I have problems with the byte and packet counters in firewall rules. They’re not counting correctly; two identical rules, one to log, one to drop and they show different values. Plus, any amendments to the rules and I get huge spurious values in many of the counters.
Is your’s an upgrade from 2.8 as well? I’m trying to work out if it’s worth clearing the configuration and typing it again from scratch.
Hoping for the first point release soon
Andrew
I did attempt to import a 2.8 config, but I doubt there’s anything left of it after all the changes I’ve made so far… 
I’ve looked through a config-dump, but can’t see anything weird…
what does not work exactly ?
The mangling works fine it seems (I can see the various mangles counting packets/bytes). However, in the Queues they are not ‘seeing’ any traffic, and therefor not doing any shaping.
The rules worked fine on a 2.8 system, so they should function on a 2.9 as well, right?
I found it had something to do with the parent queue setting. When using global in global out as parent queues they did not count. I had to set interface as parent but wen’t back to V2.8 in the end as I could not find out why?
So you’re saying that the global parent queues don’t work, but the individual interface parent queues do work? Hmm… Not quite the way it should be, but at least it would enable me to do SOME queueing… I’ll try it out as soon as I’m home! 
Here is an example of my problem:
I have the following rule in /ip firewall mangle:
chain=prerouting in-interface=!2_DMZ protocol=tcp dst-port=22 action=mark-packet new-packet-mark=SSH-local
And the folloowing queue in /queue tree print:
name="SSH-local" parent=global-in packet-mark=SSH-local limit-at=128000 queue=default priority=2 max-limit=5000000 burst-limit=0 burst-threshold=0 burst-time=0s
The queue ONLY sees traffic with the parent set to global-in. If I set it to a specific interface, no traffic gets registered. I thought global-in was the total of all interfaces? Doesn’t that mean that if I were to specify (at least) one of interfaces it should show traffic as well?
NB This is with version 2.9.1
I’m afraid I don’t know?
I use global-in and global-out as the parent queues on my 2.8 system and I just know that happens on 2.9 because it happened to me too. You are right it doesnt seem right and I can’t understand the logic?
Hopefully somebody else can tell us why this is the case?