SummaryWhen looking at the Real Time Monitor, it is possible that some traffic coming from Google Servers (especially when the same client IP has a Youtube session open) will be incorrectly classified as ICMP traffic
OverviewThe Exinda classifies traffic based on L7 definitions. When new applications, protocols or other changes to currently existing classifications come out, new classifications must be made to deal with the update. These occur on a regular basis and are put into the Exinda firmware when an update is warranted.
QUIC (Quick UDP Internet Connections) is a new protocol created by Google to provide the same type of security and lower latency involved with TCP. It was originally created in 2012, but its reach has grown to present day. QUIC is implemented on all Google servers - Gmail, Google Docs, Youtube, Google Hangouts - to test and improve the protocol. QUIC support was implemented into Google Chrome as an experimental add on in version 29. As a result, by default, all connections between Chrome and Google Servers will use QUIC instead of standard UDP if applicable. This includes Youtube connections.
In the Exinda, it has been seen that Youtube traffic from clients running Chrome to Youtube servers is being misclassified as ICMP in the Real Time Monitor, even though the traffic is known to be QUIC behind the scenes. This misclassification will not happen all the time (ie, if clients are using another web browser, or the server doesn't establish a QUIC connection) but it can be visible.
CauseIn v7.0.3 update 1 and lower of the Exinda firmware, there is no built in definition for QUIC traffic. As a result, it is just classified in general as "udp port [source] -> [destination]" traffic. The general and standard Youtube connections are made under TCP and are shown from the same client in the real time monitor along with these "udp port" classifications. On rare occasions, depending on the UDP ports used, the misclassification can show as ICMP traffic to a Youtube server in the 18.104.22.168/16 subnet.
WorkaroundOne possible workaround to avoid this misclassification is to disable QUIC in clients' Chrome browsers.
- In Chrome, navigate to chrome://flags (to get to the internal flags settings of the browser)
- Find "Experimental QUIC Protocol" under the list of items and ensure that the setting is set to "Disabled"