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?

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.

@TeleRiviera 

 

smb.support.it@tp-link.com