Currently, Omada Controller provides a detailed breakdown of categorized network traffic across various application types (e.g., Streaming, Social, Gaming, Business). However, in scenarios where certain traffic types are unclassified — due to encryption, unidentified protocols, new apps, or missing signatures — there is no fallback category for such traffic. This results in potential gaps in network visibility and makes it difficult to account for the total bandwidth used.

In comparison, other platforms like UniFi include an "Unknown" traffic bucket to capture any traffic that cannot be classified. This is extremely useful for:

• Monitoring unidentified or suspicious traffic

• Understanding gaps in DPI or classification coverage

• Ensuring total traffic visibility and accountability

Suggested Implementation:

• Introduce an "Unknown" category in the traffic analytics dashboard.

• Any traffic that doesn't match known application signatures or protocols should be grouped here.
   

This addition will greatly enhance network visibility and make Omada a more robust solution for admins who require complete traffic transparency.

(Description generated by ChatGPT 😉)

UniFi -> 

Omada ->