CRS326 and priority tagging bug

Dear Mikrotik (devs ?) and users,

I’m currently own a CRS326 switch with ROS 7.4
I need to be able to do 802.1p tagging for selected egressing packets, based on fw or bridge filter rules.
I tried different setup with no luck :

  • Set priority in mangle fw rule
  • Set priority in bridge filter
  • Set mark in mangle, then a bridge filter rule
  • Set a DSCP (and hope that priority mapping come at rescue)

NB : a ticket support has been raised (SUP-80065), the bug confirmed, but there is no ETA on the fix.
Is it possible to plan the fix in a next release not so fr from now ?

Best regards.

Forgot to say that the issue seems to be linked to the fact that the priority set from cpu is dropped somewhere in the packet flow.
Nonetheless, additionnal tests a vlan priority can be tagged using a switch rule.

To sum up :

  • vlan pri with Mangle or bridge filter : KO
  • vlan pri with Switch : OK (but too few settings available)

@Mikrotik : could it be fixed pls ?