How to configure DPI on Omada Gateway via Omada Controller
G36W-4G , TL-ER7206 , ER7206 , ER8411 , ER707-M2 , G36 , ER706W-4G , ER7406 , ER706W , ER605( V2 ) , G611
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
Contents
This article introduces how DPI works and how to configure the function on the Omada Gateway via the Omada Controller.
- Omada Controller (Software Controller / Hardware Controller / Cloud-Based Controller)
- Omada Gateway (DPI supported)
Deep Packet Inspection (DPI) can help users identify, analyze, and control application-layer traffic in the network. The DPI engine includes the latest application recognition signatures to track which applications are using the most bandwidth. Users can better manage and distribute network traffic through DPI. When DPI is enabled, the device will send the forwarded traffic to the local DPI engine for analysis, so as to determine and identify the type of traffic. When Logging Traffic is enabled, the device will collect and save the results of traffic analysis.
Follow the steps below to configure DPI.
Step 1. Launch the Controller and go to Settings > Network Security > Application Control > Deep Packet Inspection. Enable Deep Packet Inspection. Note that enabling DPI only activates the inspection capability. If you need to block or control the traffic of certain applications, further configuration is required. Logging Traffic determines whether to record the DPI application statistics logs. Clear Data allows you to select and clear the logged DPI data records.
The Application List page allows you to view all the supported applications, as shown in the following figure.
Step 2. Go to Rules Management to create new App Rules. Click Create New Rule. Specify a time range for the rule to take effect in the Schedule field. When QoS is enabled, the applications in this rule will be added to the corresponding QoS class to limit their rate. In the Select Apps section, search and select one or more applications to add to the rule.
Step 3. Go to Application Filter and click Create New Application Filter. In the Select Rules section, select one or more rules created in Step 2.
Step 4. Go back to the Deep Packet Inspection page and configure the Restriction policy in the Assign Restriction section. Click Create New Assign Restriction and select the Network and the Application Filter created in Step 3 in the pop-up window. Click Confirm and the policy will take effect and block the applications.
Step 5. If you have enabled Logging Traffic in Step 1, you can go to Statistics > Application Analytics to view the traffic statistics of different applications.
- In the Overview section, the pie chart represents the proportional breakdown of all types of network traffic. The information on the right displays the specific application types and their proportions.
- The Categories section displays the detailed traffic information of specific applications under each category. Click on the traffic data or the More button to navigate to a more detailed statistics page. This will allow you to view the information about the specific devices that are accessing the applications.
- The Apps section displays the traffic statistics on all the applications, including the allowed and blocked ones. Allow Apps provides traffic data information, while Block Apps displays block times.
- The User section provides traffic statistics of all the connected clients in the network.
Now you have configured DPI on the Omada Gateway and can view the traffic statistics of different applications and clients in the network.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Why does Application Analytics fail to display any traffic statistics even though I have configured DPI?
Re: Ensure that DPI and Logging Traffic is enabled on the gateway, and make sure that you are accessing the applications through the gateway. Generally, it takes around 5 minutes for the application traffic statistics to be reported to the Controller. Please note that if you use a local Controller (i.e. Software/Hardware Controller), the DPI application traffic is reported to the Controller through a specific port (TCP port 29815). In this case, check your local firewall policy to ensure that this port is not being blocked.
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au