Traffic from devices connected to these ports simply goes to the untagged / native VLAN of the AP, which is the management VLAN.
I do believe that VLAN tagging on those ports is not currently a supported feature in the Ruckus Cloud offering. Keep watching for updates.
It is supported with other control options such as Unleashed and Smartzone and is also supported on the H510 in Cloud as of the next scheduled release (Jun-2018).
The release is still a couple weeks away, and should be completely updated by End of June.
· LAN port
· Port Type
· VLAN untag ID/Management VLAN – 1 (mgmt. VLAN always 1)
· Access – End users and VLAN-unaware workstations commonly reside on access links. All ports are in ACCESS mode assigned to the default VLAN (VLAN 1). Ports set to Access mode belong to one VLAN only.
· Trunk – On VLAN trunk links, all frames must be tagged with the respective VLAN ID’s. The native VLAN must match on all switches in the segment. (VLAN 1 is default Native VLAN). The native VLAN is NOT tagged.
· General – similar function as Trunk ports but passes only the VLAN traffic that is defined by the user.