Hi,
is there any way to set priority for IPv6 packets?
ipv6/firewall/mangle - there is not action “set priority” -bug?
set priority does not do much anyway…
you can mark packets and handle them differently in a queue tree, that works OK.
Don’t be silly 
MikroTik NV2 wireless protocol has QoS already fully integrated (IEEE 802.1D-2004)
you can set priority for wireless traffic, and there is only IPv4 support, but none for IPv6 traffic, what is pity.
you can educate yourself here, for example… https://mum.mikrotik.com/presentations/US13/lutz.pdf
Ok for NV2 yes, that is about the only exception.
We never use that, on links we normally use Ubiquiti products and they don’t need that complicated config
as they directly derive the priority from the DSCP field in the IP header. So we make sure the DSCP is correct
(possibly by mangle on the ingress) and don’t have to worry about it anywhere in the network
But indeed, in that case a set priority could be useful for you.
Yes, in all other cases.
E.g. when you have connected a router between an ISP modem and your local network using ethernet ports.
In that case setting the priority will do absolutely nothing.
(people may think it can be used to give priority to certain traffic, but it really does not work that way)
I like this guys too much!
they say, that something is useless… If you don’t use something, it is not meaning, that it is useless..
in old world, we used call them Lamer
Set priority is not only useful for NV2:
- It is used to apply MPLS experimental bits for MPLS QoS
- It is used to apply VLAN priority for other vendor wireless systems that use VLAN priority for QoS
- Set priority from DSCP high order bits option allows you to handle all 64 DSCP values in QoS with 9 mangle rules instead of 64
It is past time that IPv6 mangle had ‘set priority’ - please add this feature MikroTik!
+1000 YES, we want it back too
Yeah I came across a case today where using the Torch utility on an IPv4 only network I saw a Mac sending Airplay video to an AppleTV using DSCP value 32 on an fe80: address. Sure, I’ll just use the IPv6 mangle action set-priority from-top-3-DSCP bits to allow WMM to prefer these packets for transmission…
No such luck.
So add another dot point in above for priority being used for WMM, not just NV2.
I am sure it’s just a handful of lines to add to the IPv6 code and can be easily added to 6.41. Right? RIGHT?
Whomever ends up here: this is still the case in both latest v6 and v7. I have contacted support about this and, apparently, they don’t have enough user requests to implement this feature.
So, if you care, please create a ticket at https://help.mikrotik.com/servicedesk/servicedesk
It is still the same old story “IPv6 has no priority, no customer is ever asking for this”.
That was the answer I got in that 2017 timeframe, it is still the answer they give today.
In v7 the IPv6 support is slowly being improved, we can only hope that this feature gets implemented there.
But first v7 has to be on-par with v6 w.r.t. existing features, so people can move over and they no longer have to maintain two versions.
I agree.
My note is about that woes on the forum carry much less value than an “official” ticket. I encourage everyone to re-file the feature request. Referring my ticket (SUP-72267) may help their support to group the requests.