I would like to update a previous statement I made in my post where I described how to perform rule redirection according to the traffic name seen in "App Analysis".
Initially I guessed that the 2nd character of any packet mark was being used to signify a packet priority which corresponded to it's assigned device priority. It actually does NOT.
The 2nd character serves as a LAN client identifier instead. It's actually more than just the 2nd character. More specifically, bits 3-10 are being used to describe the LAN device so it also spills over into the 1rst & 3rd hex characters.
As an updated to my previous port, an assigned packet mark should be viewed as if it was partitioned into the sections shown below:
(I know direction has 4 possible combinations, but I haven't seen "00" or "11")
This is a shame, as I needed identifier that corresponded to each an individual packets "device priority" to fix the priority assignments available in bandwidth monitor.
I cannot really work with a client identifier as I observed clients receiving different identifiers upon re-connecting to the network with a previously assigned dhcp address.
I wish they would shave off 3 extra bits from "specific traffic type" (positions 17-19) and repurpose those as packet priority.
--
On another note, assigning a device priority via bandwidth monitor on fw v384 behaves differently than v380. Either way, dead end, on this modification I was planning.
Originally bandwidth monitor device priority was expressed by a sub class priority assignment.