WiFi Network not passing VLAN

Hello JohnMLCL​ 

JohnMLCL wrote:

(phone is able to connect to the WiFi, but it gives a 'no internet' error, and assigns an ip of 192.168.10.x .... I do not have any DHCP running on any vlan that assigns at x.x10.x)

Have by accident defined the specific SSID  for that WiFi network to NAT Mode? Than the AP will operate a local-only IP subnet including a DHCP server for that SSID.

Local Web UI; Advanced -> Addressing and Traffic -> NAT Mode

resp.

WLAN -> SSIDx -> Network Settings -> Addressing and Traffic -> NAT 

...and some subnet address and mask somehow matching 192.168.10.x

This would make the WAP acting as a NAT router, hiding all traffic under the WAP configured LAN IP address however. 

JohnMLCL wrote:

I am having issues with my Insight Managed WAC540 to properly connect to a VLAN.
If I send data untagged, it works perfectly fine on the default VLAN for the device, but I assign a SSID to be on a given VLAN, and it just doesn't connect to the VLAN.

Very unclear.

Talking of the WAP "LAN" interface which you intend to operate on a dedicated subnet on a tagged management VLAN?

Hello!

On the WAC540, you need to keep the management VLAN untagged so the AP can reach Insight, and then tag any SSID VLANs on the switch port. If clients connect but get a 192.168.10.x address, that means there’s no DHCP server on the VLAN you assigned to the SSID, so they self‑assign. The fix is to configure the switch port as a trunk with the native VLAN untagged and the SSID VLANs tagged, confirm the SSID is mapped to the right VLAN in Insight, and ensure DHCP is available on that VLAN. That way, WiFi clients will join the correct VLAN and get proper IPs.