Guys- the DPI reports are great but we need to understand better what “HTTP Connect” and “SSL” traffic actually mean to the usages we are seeing. That classification needs to include the URLs of that traffic so we can traffic shape or block specific traffic. Many of our competitors, Juniper, Cisco even InHand allows this type of traffic detailing.
I 100% second this as a critical feature. Even troubleshooting is currently very difficult because we have to setup a syslog server and send logs to it, before we can simply see if something is being blocked.
Agreed! I’m still using Meraki devices to manage fixed networks and using Peplink as modems only due to Meraki having better layer 7 and hostname reporting features I’d rather get rid of an extra device and save my clients $$$$.
This would certainly be the next step in making the DPI reports useful to network managers. Please consider adding more in depth reporting so that this feature can help position Peplink better in terms of the DPI functionality.