DPI is enabled but Application Analytics isn't populating
DPI is enabled but Application Analytics isn't populating
I have enabled DPI and setup a rule, application filter of networks (Screenshots coming) and prior to created a rule the application analytics (logs) were populated but now they are not:
DPI looks like this:
As you see I have a restriction created that uses a filter "Torrents" that contains all the P2P things you have listed in the applications. Is that causing DPI not to log everything? It logged for the first few days and then when I added the torrents restriction it stopped logging anything.
Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi All,
Starting from Omada Controller v5.9, the controller needs to use port TCP 29815 to receive Device Info, Packet Capture Files, and DPI Application Statistic Data from the Omada devices. Please confirm that the firewall/anti-virus software doesn't block port 29815. The related Knowledge Base article has been updated, please refer here.
- Copy Link
- Report Inappropriate Content
@Hank21 this fixed my issue. I added this port to the docker defined ports.
- Copy Link
- Report Inappropriate Content
@OrangeStreet I'm very shamed about this, it only evidences we don´t read the documentation. Open the ports solves the problem. Thanks!
- Copy Link
- Report Inappropriate Content
@Hank21 In my case as the person who opened this thread, opening the port was not the solution - that was already done. I had to reboot, so there still may be instances where others have to reboot the controller to make it work. There was at least one other example in the comments of this thread where that was the case. In my mind the original reason I opened this thread was not solved unless a reboot is considered a viable solution.
Thanks!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2634
Replies: 14
Voters 0
No one has voted for it yet.