How to manage Omada devices at different sites across Internet using Omada Controller

As shown below, HQ and branch office are connected with each other with the Internet. In HQ, there are TP-Link Omada Controller and TL-ER7206 in subnet 192.168.1.0/24. In the branch office, there are EAP660 HD, TL-SG3210 and TL-ER7206 in subnet 192.168.0.0/24.

Step 1. Configure Port Forwarding rules on TL-ER7206 in HQ for Controller Host (192.168.1.185)

Please go to Transmission – NAT – Virtual Server and configure a virtual server for TCP&UDP port, ranging from 29810 to 29814.

Configuration screenshot of Port Forwarding in standalone mode.

Step 2. Three methods for Omada Controller to discover the Omada devices in the branch office.

• Method 1: Discovery Utility

Run Omada Discovery Utility in Branch Office, select the Omada devices, and click “Batch Setting. Fill in the Controller Hostname/IP with WAN IP address of TL-ER7206 in HQ which is 172.30.30.199 and the Username/Password of the Omada devices. At last, click “Apply”. The default username/Password of the devices are admin/admin. If the Username and Password of Omada devices are not the same, please manage the devices one by one.

Configuration screenshot of the Omada Discovery Utility

• Method 2: Controller Inform URL

In Standalone mode, please go to System Tools/System-Controller settings of every Omada device, fill in the Controller IP/Inform URL with the WAN IP address of TL-ER7206 in HQ which is 172.30.30.199. Then click Apply.

Configuration screenshot of TL-ER7206 Controller Settings in standalone mode.

Configuration screenshot of TL-SG3210 Controller Settings in standalone mode.

Configuration screenshot of EAP660 HD Controller Settings in standalone mode.

• Method 3: DHCP Option 138

Use Omada Discovery Utility or set Controller Inform URL to adopt the TL-ER7206 in branch office. And then go to Settings > Wired Networks > LAN > Networks, click in the ACTION column of the LAN where the DHCP clients are located. Enable DHCP Server and configure common DHCP parameters. Then click Advanced DHCP Options and specify Option 138 as the controller’s IP address, which is the WAN IP of TL-ER7206 in HQ. Click Save.

To make DHCP Option 138 take effect, you need to renew DHCP parameters for the DHCP clients. One possible way is to disconnect the switch and EAP and then reconnect them.

Note: If you do not use Omada Gateway, you also can use DHCP Server which supports option138 feature to finish the configuration.

Configuration screenshot of DHCP138 in Omada Controller.

Step 3. Adopt the Omada devices in Omada Controller.

After finishing the configuration of the Omada devices in the branch office will appear in the “pending” list of Omada Controller, which means you can click the tick button in the red circle and manage these devices now.

Note: If you have adopted a gateway in the default site, please click “Add New Site” in the drop-down list of Sites and configure the parameters of the branch office. Because one site can only adopt one gateway.

Screenshot of Add New Site in Omada Controller.

Screenshot of Omada devices in Omada Controller.

Related Articles:

How to set up Port Forwarding feature on TP-Link SMB Router (new UI)?

How to Install TP-Link Omada Discovery Utility on Windows and macOS PCs?