Open andrew-dev-1 opened 4 days ago
I can't determine the cause of the problem without a traffic sample that is correctly classified by ndpiReader.
Sure, there are traffic packet samples attached
google_drive_packets_1.pcapng.zip google_drive_packets_2.pcapng.zip google_drive_packets_3.pcapng.zip google_drive_packets_4.pcapng.zip google_drive_packets_5.pcapng.zip google_drive_packets_6.pcapng.zip google_drive_packets_7.pcapng.zip google_drive_packets_app_sync_with_web.pcapng.zip google_drive_packets_web_1.pcapng.zip google_drive_packets_web_2.pcapng.zip google_drive_packets_web_3.pcapng.zip
nDPI only detects GoogleDrive traffic with the names "drive-thirdparty.googleusercontent.com" and "drive.google.com". ndpiReader does not classify your traffic samples as GoogleDrive. I can't help you.
Hello, nDPI team
Describe the bug
The nDPI doesn't track the Google Drive traffic app down. Also, the Google Drive website traffic isn't caught.
Expected behavior
The nDPI tracks down the Google Drive desktop app traffic and the Google Drive website traffic.
Obtained behavior
We're using the nDPI project to catch the traffic. It misses traffic for the Google Drive desktop app and the Google Drive website.
nDPI Environment: