How to configure Quality of Service on Omada Gateway via Omada Controller

G36W-4G , ER7206 , ER8411 , ER707-M2 , ER7412-M2 , ER706W-4G , ER605 , ER706W
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. Please note that product availability varies by region, and certain models may not be available in your region.
Contents
Objective
This article describes how to configure Quality of Service on Omada gateway via Omada Controller.
Requirements
- Omada Gateway series
- Omada Software Controller / Hardware Controller / Cloud-Based Controller
Introduction
Omada Gateways supports Quality of Service (QoS) to identify, classify, and mark incoming traffic. With the QoS feature, you can intelligently allocate and utilize network bandwidth based on the network's status and traffic information.
Network Requirements: A home network user uses IPv4 to access the internet, with a total bandwidth of 1000Mbps. The requirement is to divide the home network into three categories: Host, IoT, and Guest, and achieve the following network bandwidth allocation:
- Limit the internet bandwidth for the Guest network to 20 Mbps and restrict the IoT network's internet bandwidth to 10 Mbps to ensure the Host network performance.
- Set a maximum bandwidth limit of 20 Mbps for FTP (or any other protocol) traffic to prevent excessive bandwidth consumption by large FTP downloads, which could impact other applications.
- Ensure high priority for VoIP service traffic.
Other traffic that doesn't fall into the above categories will not be subject to bandwidth restrictions.
In this example, you can configure Quality of Service as follows.
Configuration
Step 1. Log in to the Controller via web browser, go to Site Settings > Profiles > Groups to configure specific IPv4 group to identify IoT network and Guest network, as shown in the figure below. Here, you can also configure the IPv6 group for IPv6 services.
Step 2. Go to Transmission > Quality of Service > Bandwidth Control to allocate bandwidth resources to different categories of traffic on the WAN based on actual usage. Four classes are available: Class 1, Class 2, Class 3, and Others.
- Set Inbound/Outbound Bandwidth as 1000000.
- Specify Guest network traffic as Class 1 and limit the bandwidth to 20Mbps: As shown in the figure below, set the Class 1 upstream to 1000 Mbps x 2% = 20 Mbps and the downstream to 1000 Mbps x 2% = 20 Mbps.
- Specify IoT traffic as Class 2 and set it to 10 Mbps, 1% of the total bandwidth.
- Specify FTP traffic as Class 3 and set it to 20 Mbps, 2% of the total bandwidth.
- Others cannot be configured. The remaining bandwidth after allocating for Class 1, Class 2, and Class 3 is 95%.
Step 3. Go to Site Settings > Transmission > Quality of Service >Class Rule to configure Class Rules. Configure the parameters for the Guest_network_v4 as shown in the figure below.
- IP Version: This identifies IPv4 traffic and IPv6 traffic.
- Local Address: This identifies the source address of the traffic. Select the IP Group configured in Step 1 to differentiate the network.
- Remote Address: This identifies the traffic destination address. If there are no specific requirements to restrict access to specific websites, it is generally set to IPGROUP_ANY.
- DSCP: This identifies the DSCP field of the traffic (located in the IP header) used to classify the traffic's quality of service.
- Service Name: This identifies the traffic type based on the source and destination ports of the packets.
- QoS Class: Select from the classes set in Step 2 to apply different bandwidth limits to the traffic.
The configuration of the IoT_Network_v4 and FTP traffic is similar to the Guest network.
Note: The Service Type has 13 rules by default, as shown in the figure below.
If the default rules cannot meet your need, click Add to configure a new Gateway QoS Service.
Step 4. Go to Site Settings > Transmission > Quality of Service >VoIP Prioritization to enable the first priority for VoIP traffic as shown in the figure below. With this feature enabled, the Omada Gateway prioritizes SIP/RTP packets with the specified destination port (typically port 5060) in congested network environments.
Verification
Go to Insight > QoS Data to view the WAN’s real-time traffic statistics of each class, as shown in the figure below. With the real-time traffic statistics, you can determine if the traffic classification and bandwidth control are working.
Conclusion
You have now successfully configured Quality of Service on the Omada Gateway.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Related FAQs
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
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 .
Your Privacy Choices
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 .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_banner, tp_privacy_base, tp_privacy_marketing, 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
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
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or