-
Home
SOHO Switches
Keeping your home wired for quality connections
Accessories
Everything else you need for a connected lifestyle
-
Smart Home
Cloud Cameras
Keeping an eye on what matters
Smart Plugs
Smarten up your home devices
Smart Bulbs
Light for every occasion
-
Business
Omada Access Points
Professional business Wi-Fi with centralized management
Omada Cloud SDN
The smarter cloud solution for business networking
Switches
High-Speed wired networking from L3 managed to unmanaged
Pharos Wireless Broadband
Ideal for long range wireless broadband networking
SafeStream Router
Secure VPN and Load Balance gateways to the business
VIGI Surveillance
VIGI video surveillance is dedicated to your security
-
Service Provider
DSL
Capable of high-speed network and integrated broadband applications
Wi-Fi Router
The reliable choice for home networking
FTTx
The leading technology for delivering gigabit Internet services
Range Extender
Easily expand your Wi-Fi coverage.
LTE
Maintains internet access wherever you go.
How to manage EAPs at different sites across Internet using Omada Controller (via NAT Port Forwarding for Controller Host with EAP Discover Utility)? (Old UI)
21034 As shown below, HQ and Branch Office are connected with each other. In HQ, there are TP-Link EAP/Omada controller, EAP1 and TL-ER6120 (VPN Router) in subnet 192.168.1.0/24. In branch office, there are TP-Link EAP discover utility, EAP2 and TL-ER6120 (VPN router) in subnet 192.168.0.0/24.
This document will introduce how to manage EAPs at different sites across Internet using TP-Link EAP/Omada controller (via NAT port forwarding with EAP discover utility).
Step1. Configure Port Forwarding rules on TL-ER6120 in HQ for Controller Host (192.168.1.253)
Please go to Advanced – NAT – Virtual Server and configure virtual server for TCP&&UDP port, ranging from 29810 to 29813.
Step2. Settings on PC that is running EAP Discover Utility in Branch Office
Run EAP discover utility, and fill in the Controller Hostname/IP with the WAN IP address of TL-ER6120 in HQ which is 172.30.30.138) and the Username/Password of the EAP (admin/admin by default). At last, click “Apply”.
Note: After EAP successfully adopted by EAP/Omada Controller, you don’t need EAP Discover Utility any more, thus you can remove the PC which is running the EAP discover utility from the network.
Step3. Run EAP Controller. The EAP which has been configured by EAP discover utility just now will appear in EAP/Omada controller’s “pending” list, which means you can use EAP controller to adopt and manage this EAP now shown as below.
Your feedback helps improve this site.