You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way it is defined currently it seems like the SAI API for DASH ACL rule and the bmv2 implementation require a packet to match all tags in the rule to be considered a rule hit. Whereas the intended behavior is for packet to match at least 1 tag in the rule for the rule to be considered a hit.
In this context, need clarification on whether the SAI API for DASH ACL rule will have only 1 tag to match in each rule. This will ensure that the bmv2 behavior is inline with the tag match requirement.
The text was updated successfully, but these errors were encountered:
The way it is defined currently it seems like the SAI API for DASH ACL rule and the bmv2 implementation require a packet to match all tags in the rule to be considered a rule hit. Whereas the intended behavior is for packet to match at least 1 tag in the rule for the rule to be considered a hit.
In this context, need clarification on whether the SAI API for DASH ACL rule will have only 1 tag to match in each rule. This will ensure that the bmv2 behavior is inline with the tag match requirement.
The text was updated successfully, but these errors were encountered: