How to Manage CAPs in Different subnets Using TP-Link AC Controller (Using TP-Link AC Controller as the DHCP Server for the CAPs)?

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 AC controller AC500 in VLAN1 (192.168.0.0/24) to manage CAP in VLAN2 (192.168.1.0/24). The gateway Router is TP-Link SMB router TL-R480T+.

This document will introduce how to manage CAPs in different subnets using TP-Link AC controller (using TP-Link AC controller as the DHCP server for the CAPs). For the configurations of multi-nets NAT function on TP-LINK SMB router, please refer to: https://www.tp-link.com/support/faq/887/ .

Step5. After all configurations, we can check CAP’s status in AC controller’s “AP Status” page. Here the following screenshot shows the CAP in VLAN2 (192.168.1.0/24) subnet managed by AC controller in VLAN 1 (192.168.0.0/24) subnet.

Create a SSID, bind it to the CAPs and connect your client device to CAP’s wireless network to see if you can go to Internet normally. It turns out you can go to Internet normally and AC controller can manage CAPs in different subnets.

Q&A

What if AC can discover CAP, but client device has no Internet Access?

Answer: Check if you have set up multi-nets NAT function on gateway router and set up the correct static routing entries on L3 switch. Please refer to: https://www.tp-link.com/support/faq/887/ . Also, please check the DHCP Server Settings, and make sure you have set the right Default Gateway and DNS Server IP.

Why my client device cannot get the IP address from DHCP server?

Answer: Please make sure that you have chosen “For AP and Client” as AC controller DHCP server’s Target.