Summary of supported WiFi vendors

	Max PSKs	Traffic isolation	Groups	Roaming
Extreme Networks	5000	Yes	Yes - shared PSK only	Yes
Cambium Networks	5000	Yes	Yes - VLAN by group	Yes
Juniper Mist	5000	Yes	Yes - VLAN by group	Yes
Meraki	5000	Yes	Yes - Group Policy by Group	Coming soon
Huawei	-	Yes	Yes - VLAN by group	No
TP-Link Omada	128 (upgrading soon!)	Yes	Yes - VLAN by group	No

Extreme Network - Extreme Cloud IQ

Function	Support	Notes
Traffic Separation	Yes	Cusna relies on ExtermeCloudIQ PCGs (Private Client Groups) to secure traffic. It does not manage VLAN assignment. All clients are assigned on the same VLAN as per your Network Profile configuration.
Groups	Yes	By default, Members of the same Group will share the same PSK but have individual accounts (useful for Cloud Identity system integrations)
Roaming	Yes	You need to assign the same Network Policy to all Networks

Other notes

• To do not separate traffic, simply disable PCGs in the Extreme Network Policy setup

Cambium - cnMaestro

Function	Support	Notes
Traffic Separation	Yes	Cusna relies on automatic VLAN assignment to separate traffic of Accounts and Groups
Groups	Yes	When VLAN management is enabled, Group Members are assign the same VLAN of the Group. By default, each Group Member has an individual PSK.
Roaming	Yes	You need to assign the same WLAN Profile to all AP Groups (locations/sites). If you use VLANs, you need to configure the same VLANs in all Networks.

Other notes

• You need cnMaestro X license to be able to connect cnMaestro to Cusna

Juniper - Mist

Function	Support	Notes
Traffic Separation	Yes	You can enable the native Mist capability (Personal WLAN) to separate traffic of clients using different PSKs. In the alternative, you can rely on Cusna auto VLAN management to assign automatically VLANs to account.
Groups	Yes	Be default, when Groups are enabled, each Group Member will have an individual PSK. When VLAN are enabled, all Group Members share the same VLAN. In this case you should disable the native Personal WLAN setting in Mist dashboard, otherwise clients of the same group won't be able to see each other.
Roaming	Yes	When setting up Cusna, you can opt for Site-level or Org-level PSKs. Org level PSKs allows clients to connect with the same PSK in multiple locations. If you are using VLANs, you would need to configure the same VLANs in all Networks.

Cisco Meraki

Function	Support	Notes
Traffic Separation	Yes	Cusna relies on the native Meraki Wi-Fi Personal Network (WPN) to achieve traffic isolation.
Groups	Coming Soon!
Roaming	No	iPSKs have Network scope in Meraki and there is no solution to make it work (other than replicate them in each Network)

Other notes:

• At this time, Meraki iPSK without WPN is limited to only 50 PSK. So, for most cases, enabling WPN is required. Make sure to read about the limitations and implication of using WPN (see Meraki WPN Limitations)

• For each Account, you have to assign a Network Policy (which include VLAN), however it is not practical to have a Network Policy for each individual. Network Policies are meant to be used to to differentiate QoS and VLANs of Groups. All individual Account most commonlty are assigned with the same Network Policy

Huawei - iMaster NCE-Campus

Function	Support	Notes
Traffic Separation	Yes	Cusna relies on automatic VLAN assignment to separate traffic of Accounts and Groups
Groups	Yes	When VLAN management is enabled, Group Members are assign the same VLAN of the Group. By default, each Group Member has an individual PPSK.
Roaming	No	Unless you use the same Site to handle the network in multiple Networks, roaming is not currently supported