Hmn ... I would try the same as with the security policy: post-NAT destination zone and pre-NAT destination IP.
... and if this does nlt work, simply create different rules for testing with differdnt QoS classes assinged and check which QoS class will the connections have assigned.
QoS is applied on the egress interface (post-nat), whereas NAT is determined based on the pre-NAT IP route lookup
is your NAT going to be a traditional untrust to untrust, translated to an internal IP, or are you intending to receive connections on the untrust, apply NAT (to another external IP) and then send packets back out of the untrust ? (u-turn on the outside ? )
in the former, you'd set your NAT untrust to untrust, and your QoS + security policies untrust to dmz/trust
in the latter, you'd have all your policies set to untrust-untrust
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!