topic Re: Device Access Policy not working in Unleashed

Device Access Policy not working

aeidson — Fri, 17 Oct 2025 19:04:12 GMT

Have tried to setup a Device Access Policy on a Wifi that utilizes Radius using 802.11x with WPA2/WPA3 encryption to block iOS or Android devices.

I have setup a policy Allowing All and denying Android and iOS..

I have setup a policy Deny All and allowing Windows and MacOS.

In both instances when I apply the policy to the WiFi it kicks everyone off and won't allow anyone to authenticate to the WiFi.

Any ideas on where to go from here?

Re: Device Access Policy not working

Mayank — Mon, 20 Oct 2025 04:13:07 GMT

Hi Aeidson,

Thank you for posting your query.

My understanding of the issue is that when a Device Access Policy (DAP) is applied on an 802.1X (RADIUS) WLAN in Ruckus Unleashed, all clients are unable to connect as the DAP conflicts with the 802.1X authentication process.
Please correct me if I have misunderstood the issue.

To assist you further, kindly provide the following information:

The Unleashed firmware version currently running on your network.

Whether the issue occurs across all Access Points or specific ones.

The total number of Access Points and clients connected to this WLAN.

The RADIUS server in use (e.g., Windows NPS, FreeRADIUS, or a Cloud-based service).

Whether all clients are unable to connect once the policy is applied, or only specific device types.

Confirmation if the WLAN is configured with WPA2-Enterprise or WPA3-Enterprise (802.1X).

Whether Dynamic VLAN assignment is enabled from the RADIUS server.

A short extract of the event log captured during the connection failure.

Thanks
Mayank

Re: Device Access Policy not working

aeidson — Mon, 20 Oct 2025 14:14:21 GMT

This is across all 12 of our Access points, we have firmware 200.18.7.1.302

It is using Windows NPS. The WLAN is configured with WPA2 and Dynamic VLAN is enabled on the specific WiFi network.

No clients are able to connect, in fact all connected clients get kicked off when the policy is applied as well ( Windows, Mac, iOS, and Android ) at the time of the test there were over 40 clients connected to the specific WiFI network across multiple access points.

There are no logs that I can find showing anything at this point. The only thing I am seeing is the following in the events log for our Test Network.

User[aeidson@9a:66:ec:a0:45:0e] leave WLAN[IT_Test] at AP[HR@70:ca:97:05:f3:c0] with Session Time[2.45 sec] RX Bytes[0] TX Bytes[0]

Re: Device Access Policy not working

aeidson — Mon, 20 Oct 2025 17:43:37 GMT

This is happening on all 16 APs, and they are all on firmware 200.18.7.1.302

We are using Windows NPS.

When the policy is put into place it kicks every users off all APs that are part of that WiFi network at the time. It also will not allow access to the network and the logs just show the Endpoints leaving the Wifi.. no connection details of any kind or any other messages.

This happens for Windows, Mac, iOS, and Android devices that were on WiFi network when the policy was applied. Removing it was the only way to get any device to connect.

Re: Device Access Policy not working

aeidson — Mon, 20 Oct 2025 17:59:19 GMT

This is happening for all 16 APs, we are on firmware 200.18.7.1.302

We are using Windows NPS and the Ruckus Unleashed Console shows WPA2/WPA3 there is no option for -Enterprise on either one.

the log is just showing disconnects for the end points when looking at them. No information about connection attempts or messages showing anytype of failure.

Re: Device Access Policy not working

Mayank — Thu, 23 Oct 2025 07:48:11 GMT

Hi Aeidson,

For verification purposes, could you please test the scenario on firmware version 200.17 to confirm whether the issue is firmware-specific? Kindly share the results once the testing is completed.

Thank you for your assistance.

Best regards,
Mayank