How to manage EAPs in different subnets using Omada Controller (via DHCP option 138) (Old UI)
EAP225 V3 , EAP110-Outdoor V3 , EAP225-Wall , EAP115 V4 , OC200( V1 ) , EAP225-Outdoor , EAP225 V2 , EAP245 , EAP320 , EAP110 , EAP220 , EAP330 , EAP120 , EAP235-Wall , EAP110 V4 , EAP115 , EAP225 , EAP110-Outdoor , Omada Software Controller , EAP115-Wall
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.
In the network topology below, there are three VLANs (three subnets), which are VLAN1 (192.168.0.0/24), VLAN2 (192.168.1.0/24) and VLAN3 (172.30.30.0/24). These three VLANs (three subnets) are divided by TP-Link L3 Switch (T2600G-28TS). Now we want TP-Link EAP Controller in VLAN1 (192.168.0.0/24) to manage EAP in VLAN2 (192.168.1.0/24). The gateway Router is TP-Link SMB router TL-ER6120.
This document will introduce how to manage EAPs in different subnets using TP-Link EAP/Omada controller (via DHCP option 138). For the configurations of multi-nets NAT function on TP-LINK SMB router, please refer to:
Step1. Configurations on Layer 3 switch
1. Create VLAN2 & VLAN3. VLAN2 includes port 4, and VLAN3 includes port7. The detailed VLAN settings are shown as below. Note: port4/7/16 should be configured as “Access” type.
2. Enable IP interface for VLAN1 & VLAN2 & VLAN3, and configure relevant IP addresses for these three interfaces shown as below.
3. Configure the static default routing entry which leads to the gateway router.
4. Enable DHCP Server function, and configure 192.168.1.0/24 IP address pool for EAPs. For Option138, you should fill in the IP address of EAP/Omada Controller Host which is “192.168.0.253”. And then the DHCP Server will tell the EAPs where the EAP/Omada Controller is, so that the EAP/Omada Controller and EAPs can communicate with each other among different subnets. Note: don’t forget to fill in the DNS server address.
Step2. Configurations on SMB Router
1.Configure Static Routing for VLAN1 and VLAN2 subnets.
2. Configure multi-nets NAT for 192.168.0.0/24 and 192.168.1.0/24 subnets.
Step3. Run EAP Controller. The EAP will appear in EAP/Omada controller’s “pending” list, which means you can use EAP/Omada controller to adopt and manage this EAP now shown as below.
Looking for More
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.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
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 .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
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_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
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
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
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or