Configuration Guide How to Set Up Deep Packet Inspection(DPI) on Omada Router
Configuration Guide How to Set Up Deep Packet Inspection(DPI) on Omada Router
Background:
This post provides a configuration guide to set up DPI to monitor your network traffic. The guide will show steps in Controller mode. For standalone, the steps are similar.
This Article Applies to:
Routers with DPI feature.
Application Scenario:
Configuration Steps:
1. Start your Controller and access the Organization, choose the site.
2. Go to Settings > Network Security > Application Control > Deep Packet Inspection, Enable. If you need Logging Traffic, please enable it accordingly.
3. Go to Rules Management > Create New Rule. This is choosing the apps that are being blocked.
4. Go to Application Filter > Create New Application Filter > Select Rules - Add.
4. Go to Deep Packet Inspection > Assign Restriction > Create New Assign Restriction.
5. Now, the setup is complete.
Verification:
Go to Statistics > Application Analytics. View your block result/traffic on this page.
Categories:
Apps > Allow Apps:
Apps > Block Apps:
Users:
Note:
1. Data is not instantly synced. It may take a few seconds to minutes depending on your network scale.
2. If you are not familiar with the terms of the configuration steps, please refer to the User Guide of Omada Controller and view the term explanation. Or you can click Help Center which is located on the top right corner of every Controller function.
Help Center icon.
3. The DPI Application List is stored locally and is updated through firmware updates. Please be aware that it does not synchronize with the Internet, and therefore, the list may not always reflect the most up-to-date information.
4. If your Controller does not add the DPI function, while the router has been added with this feature, due to the adaptability issue on your controller, you cannot set the DPI properly.
Related posts: No Deep Packet Inspection Option after Firmware Upgrade to 2.2.4 and Reboot - OC200 Not supported?
https://community.tp-link.com/en/business/forum/topic/628384?replyId=1289568
5. Any static routing or configuring the gateway to be the Omada router LAN IP will NOT get your traffic monitored. Clients MUST be located in the VLAN interface from and of Omada router. Put it differently, which means you are getting a DHCP IP from the VLAN interface of the Omada router.
Update Log:
May 27th, 2024:
Add an note.
Mar 28th, 2024:
Add extra notes.
Jan 31st, 2024:
Release of this guide.
Recommended Threads:
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Feedback:
- If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
- If there is anything unclear in this solution post, please feel free to comment below.
Thank you in advance for your valuable feedback!
------------------------------------------------------------------------------------------------
Have other off-topic issues to report?
Welcome to > Start a New Thread < and elaborate on the issue for assistance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Are you able to see by Application Statistics any timestamp / timelog, to determine when any application was started/streamed/used?
That is, what I mean what it should do.
If you read in a newspaper, that some accident was happen - its important to know when and where. Isnt it?
- Copy Link
- Report Inappropriate Content
Currently I use a software controller with an ER605 V2
ER707-M2 and confirmed that the firmware is the latest, but the DPI blocking function is not in effect.
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
Timothy-Hsiao wrote
Currently I use a software controller with an ER605 V2
ER707-M2 and confirmed that the firmware is the latest, but the DPI blocking function is not in effect.
1. Certain signatures require an update of firmware. They has been changed by the companies so we need to update the signature identification. This does not mean the DPI or configuration guide is not correct.
2. For the models you have, you should check the latest beta to see if there is an update to address the known issues.
This problem is known to us and some models have a beta to address this issue because of the reason explained in 1.
Please start a new thread regarding the issue. Or contact the technical support team regarding the issue or beta firmware download.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 9
Views: 11103
Replies: 13
Voters 2
