TP-Link OC200 Omada Controller Software 4.1.5Windows/Linux User Guide - Page 32
Scenario 1: Across VLANs or Subnets, Scenario 2: Across LANs
![]() |
View all TP-Link OC200 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 32 highlights
Chapter 3 Manage Omada Managed Devices and Sites ■■ Scenario 1: Across VLANs or Subnets As shown in the following figures, the controller and devices are in different VLANs or subnets. You need to set up a layer 3 interface for each VLAN or subnet, and make sure the interfaces can communicate with each other. Internet Gateway Interface 1 Switch AP AP VLAN 1 Interface 2 Omada SDN Controller Site Unified Management from One Interface Gateway Switch APs VLAN 2 Internet Gateway Interface 1 Switch AP AP Subnet 1: 192.168.0.0/24 Interface 2 Omada SDN Controller Site Unified Management from One Interface Gateway Switch APs Subnet 2: 192.168.1.0/24 ■■ Scenario 2: Across LANs As shown in the following figure, the controller and devices are in different LANs. You need to establish communication across the internet and the gateways. By default, devices in LAN 1 cannot communicate with the controller in LAN 2, because Gateway B is in front of the controller and block access to it. To make the controller accessible to the devices, you can use Port Forwarding or VPN. 30
![](/manual_guide/products/tplink-omada-software-controller-omada-controller-software-415windowslinux-user-guide-e154318/32.png)