Wireless Traffic Identified as DSCP18
This is driving me up the wall and I don't see a lot of good options, aside from pester support. We're an Aruba wireless shop and we have some WMM/QoS configured. This ends up with a bunch of event...
Forum Discussion
michaelsaw
Cato Employee
Cato EmployeeHi MichaelQ,
From the Events, It seems there is a large volume of traffic related to "dscp18".
Would you like to create a specific WAN FW rule to match this type of traffic (source: AP, destination: Any, type: dscp18, action: allow, event: disable) so that it does not show on the CMA Events?
Cheers
Not particularly. I would much more prefer that that Cato more intelligently identify traffic based on port/protocol, rather than the QoS values that the access point inserts.
What I want to avoid is a scenario where, for example, I create a firewall rule that permits a user to RDP to a server(s) where the service on the rule is RDP but that user is accidentally blocked from doing so because Cato has identified their traffic as DSCP18.
