AC500 & CAP1750 - Multi VLANS

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

AC500 & CAP1750 - Multi VLANS

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
AC500 & CAP1750 - Multi VLANS
AC500 & CAP1750 - Multi VLANS
2017-10-21 22:39:14
Model :

Hardware Version :

Firmware Version :

ISP :

Hi,

I have urchased an AC500 and two CAP1750 AP's, and I'm struggling to replicate the VLAN based setup we have on our current OLD Ruckus system.

Is there a guide somewhere that describes the process of creating several SSID's each using a separate VLAN (not 1) and physical interface on the AC500, with all AP's on VLAN1 (port 1). We have a proxy device that can sit on all VLANs to give clients IP addresses based on that VLAN tag, but my fiddling about doesn't result in DHCP working from the proxy to client. Maybe that's really the issue, how to 'relay' DHCP requests from clients on different SSID's (vlans) t the proxy via the AC500.

Hope this makes sense.

Rob
  0      
  0      
#1
Options
7 Reply
Re:AC500 & CAP1750 - Multi VLANS
2017-10-22 16:12:17
See http://forum.tp-link.com/showthread.php?99025-How-to-configure-Multiple-SSIDs-with-Multiple-VLANs-on-CAP-amp-AC-products for a How-To. Even if you don't use the devices mentioned there, it will give you an idea how to set up such a topology.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options
Re:AC500 & CAP1750 - Multi VLANS
2017-10-23 22:13:05
Hi,

Thanks for that but I think I'm still missing a bit of information. I'm still not able to get DHCP to clients on the Wireless network. To clarify, if I plug in a laptop to the port on the switch (vlan tagged), I get a DHCP address from our Proxy/Filter in the correct range - so I know the switch port is dishing out correct IP addresses via the Proxy. With the AC500 plugged into the same port (using port 2 interface), I can see the MAC address of the AC500 on the switch, and the static IP I allocated to the AC500 on Port 2 is ping-able from the switch and I can ping the Proxy from the AC500 using interface 2 - so communication between proxy and AC500 is all good. The SSID is bound to the VLAN (101) same as Interface 2, but no DHCP is getting to the client connected to the SSID. If I bind the SSID to interface 1, which is VLAN 1, wireless connectivity works & DHCP address is provided, but from a different range (as expected). So to me it looks like the client can connect to the SSID, its MAC is registered in AC500 for the client, but no IP address is provided. So my question is, is there a way to allow DHCP requests from the Client through Interface 2 using vlan101?
  0  
  0  
#3
Options
Re:AC500 & CAP1750 - Multi VLANS
2017-10-24 00:56:16

Support wrote

So my question is, is there a way to allow DHCP requests from the Client through Interface 2 using vlan101?


AFAIK the AC500 can't supply DHCP addresses to clients over VLANs. It can supply a DHCP address for the CAPs, but for the clients you will need separate DHCP servers in the subnets assigned to the VLANs. In the HowTo mentioned above this is done on the T2600G switch in step 3.2. Also make sure the CAPs are connected to the switch's trunk port if using VLANs.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#4
Options
Re:AC500 & CAP1750 - Multi VLANS
2017-10-27 20:08:16
Ok, thanks for your response. On the face of it DHCP is operating through the switch, as I said a laptop connected to the port on the switch gets an address from the VLAN, but when the AC500 port two is connected to that same switch port there is no IP address allocated to wireless clients (and yes the SSID is bound to the correct interface/VLAN). Clients on an SSID bound to an interface using VLAN1 do get DHCP responses and an appropriate IP address, so the issue seems to be VLAN oriented.

I have some VLAN experts coming to site to assist some time soon, once we have figured it out I'll post instructions.
  1  
  1  
#5
Options
Re:AC500 & CAP1750 - Multi VLANS
2017-10-28 03:22:55

Support wrote

Clients on an SSID bound to an interface using VLAN1 do get DHCP responses and an appropriate IP address, so the issue seems to be VLAN oriented


VLAN1 is the default VLAN, so traffic is untagged even on trunk ports if the PVID of the trunk is 1 *). If - for whatever reason - you want to connect the CAPs through an AC500 with the switch, make sure the AC500's port to the switch and the port to the CAPs both carry tagged traffic (i.e. by setting the PVID accordingly or by using VIDs > 1). Alternatively you could use a General port with explicit egress rule TAG.

*) From the AC500 manual: The trunk port can be added in multiple VLANs. The egress rule of the port is UNTAG if the arriving packet’s VLAN tag is the same as the port’s PVID, otherwise the egress rule is TAG.


BTW, as I learned from the other thread here about guest networks, the AC indeed can support DHCP servers for different VLANs, so this might be an alternative way to go.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#6
Options
Re:AC500 & CAP1750 - Multi VLANS
2020-05-09 23:33:01

@Supporto salve, esiste una guida per configurare il router 6120 con ac500 e cap 1750 per realizzare 3 ssid con vlan differenti?

  0  
  0  
#7
Options
Re:AC500 & CAP1750 - Multi VLANS
2020-05-11 08:31:03

@TeleRiviera 

 

smb.support.it@tp-link.com

 

  1  
  1  
#9
Options