Instructions for Managing the Omada EAP Networks
As a stepping stone helping you get started in Omada EAPs, read the instructions and determine an optimal management method in your situation, and then follow the steps provided to set up your network of each method.
Which management mode do you prefer?
-
Standalone Mode
- No extra equipment
- For 1-3 EAPs
- Separate management
- Basic functions
- Local management only
-
Controller Mode
- Omada Controller required
- For over 3 EAPs
- Central management of multiple devices
- Advanced functions and surveillance
- Local and remote management
Setup on free Omada App in minutes
1. Determine the network topology
Power up and connect your EAPs according to the typology.
2. Install Omada app
Download the Omada app on your mobile device.
3. Connect to EAP’s Wi-Fi
Connect your mobile device to EAP’s Wi-Fi. The default SSID (format: TPLink 2.4GHz/5GHz_XXXXXX) is printed at the bottom of the EAP.
4. Launch app to manage the EAP
Launch the Omada app and follow the instructions to manage the EAP. Pull down to refresh if your EAP is not in the list.
You can also configure more functions on the PC.
Using Web Browser on the PC to configure the EAP
-
If your PC is connecting to the default Wi-Fi of the EAP…
-
If your PC is connecting to the Internet via an Ethernet cable…
Using Web Browser on the PC to configure the EAP
1. Connect your PC to EAP’s Wi-Fi
Connect your PC to EAP’s Wi-Fi. The default SSID (format: TPLink 2.4GHz/5GHz_XXXXXX) is printed at the bottom of the EAP.
2. Set your PC to obtain an IP address
Set your PC to obtain an IP address automatically. Then, make sure that your PC has got the IP address, default gateway, and DNS server from the DHCP server. (What Can I do If My PC fails to get IP address )
3. Log in to the management page
To log in to the EAP, launch a web browser and enter http://tplinkeap.net in the address bar*. By default, both the username and password are admin. (What Can I Do If I Fail to Log In to the EAP via the Domain Name ).
*You can also enter the IP address of the EAP obtained from the front router to enter the management page.
4. Complete the basic configurations
After login, follow the instructions to complete the basic configurations. Please remember your username and password for later login. You need to reset the device If you forget the username and password.
Using Web Browser on the PC to configure the EAP
1. Find the IP address of your EAP
Log in to the front router* and find the IP address of your EAP according to its MAC address, which can be found at the bottom of the EAP.
*When the DHCP server is not available in your network, the EAP has the default DHCP fallback IP address 192.168.0.254.
2. Log in to the management page
To log in to the EAP, launch a web browser and enter http://tplinkeap.net in the address bar*. By default, both the username and password are admin . (What Can I Do If I Fail to Log In to the EAP via the Domain Name ).
*If you fail to log in to the EAP, please check if you have entered the right IP address and make sure you PC and EAP are in the same network subnet.
3. Complete the basic configurations
After login, follow the instructions to complete the basic configurations. Please remember your username and password for later login.
Which Omada SDN Controller do you prefer?
-
Omada Hardware Controller
- Hardware controller required
- OC200: up to 100 EAPs; OC300: up to 500 EAPs
-
Omada Software Controller
- Installed and keep running on a PC/server.
- Up to 1500 EAPs
- Technical operation and maintenance required
Quick setup on Omada Hardware Controller (OC200/OC300)
1. Determine the network topology
The network topology varies depending on your requirements. The following figure shows a typical topology for a high-availability use case.
Power up your devices and the hardware controller, make sure that they can access the internet. It takes 3 to 5 minutes for the hardware controller to initialize.
2. Log in to the Omada Cloud
Launch a web browser and type https://omada.tplinkcloud.com* in the address bar, then press Enter (Windows) or Return (Mac). Enter your TP-Link ID** and password to log in. (No TP-Link ID? Go to create one)
* With Omada Cloud Service, you can remotely monitor and manage your wireless network.
**A TP-Link ID allows you to manage your network and devices with a single account and enjoy the cloud service.
3. Add hardware controller
Click 
Controller on the left column, and then click + Add Controller and choose Hardware Controller to add your OC200/OC300.
4. Complete the quick setup and adopt devices
Follow the instructions to complete the quick setup process. Then go to the Devices page and adopt your EAPs.
Quick setup on Omada Software Controller
1. Determine the network topology
The network topology varies depending on your requirements. The following figure shows a typical topology for a high-availability use case.
2. Install Omada Software Controller
Download the Omada Software Controller from the download center. Then follow the instructions to install the controller.
Omada Software Controller is provided for both Windows and Linux operating systems (How to install the Omada Controller on the Linux system).
Ensure that the Java Runtime Environment (JRE) have been installed in your system (How to Install JRE 1.8 ). The controller requires that the system have Java 8 installed.
3. Complete the quick setup and adopt devices
Launch the software controller, and after a while, your web browser will open automatically (What should I do if I cannot start the Omada Controller ).
Follow the instructions to complete the quick setup process. Then go to the Devices page and adopt your EAPs (What should I do when the Omada Software Controller (V4) fails to discover the devices ).
*With Omada Cloud Service, you can enable Cloud Access on the controller and bind a TP-Link ID to your controller, then you can remotely monitor and manage your network.
*With Omada App, you can also manage your Omada Software Controller at a local site and remote site. Note that Omada Software Controller needs to be kept running when using Omada APP.
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 .
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