nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

R610 and Intel AX201 Connection Issues

brad303

Hello, we are using R610 AP's running firmware version 6.1.0.0.1595 (using WPA2-AES for encryption). We frequently have devices with Intel AX201 chipsets having an issues where they connect to the AP but fail to get an address. This issue is tough to recreate but seems most common if the device has been "off" WiFi for an extended period.

The wlan logs on the device show security starting, stopping, succeeded in a loop then the 802.1x authentication restarting. This will usually happen for a few minutes until it either resolves, device/wireless radio cycled on/off, or in some cases the network is reset in Windows.

Are there any issues we should be aware of or settings changes that should be made to resolve the issue. A majority of our fleet uses the AX201 chipset and we are often seeing these issues popup.

Let me know what other info I can provide and any help is appreciated!

Find more posts tagged with

AP Management

Authentication Server

Firmware Recommendation

NAND flash memory

Accepted answers

All comments

sanjay_kumar

Hi @brad303
May I know what is the driver version of the AX201 chipset? The latest one is 23.20.0.

sanjay_kumar

If it is on latest version, from the looks of it it seems we need to analyse more with the logs and captures from the client. It would be great if you can open a case so that we can gather the necessary logs and track the issue.

brad303

We have tried the latest drivers from Intel and Lenovo (these are Lenovo devices). It looks like the 23.20.0 drivers were released on the 9th so we have previously been using 23.10.0.8 (from Intel) or 22.250.1.2 (from Lenovo). Overall though these issues have been ongoing since last year. I have been collecting the wlan reports from affected devices, I have yet been able to replicate it though and just have to wait for someone to report issues.

bruno_andrade

Hi Brad,

I've seen some issues with version 22.250, where the device cannot process the probes from the AP, preventing it from 'seeing' the AP/WLAN. Upgrading the driver to version 23.20 resolved the issue.
Could you please upgrade to this driver version and check? Additionally, you might want to upgrade your SZ and APs to version 6.1.2.

If the issue persists after the upgrade, you can run the troubleshooting tool on SZ to examine the authentication steps and identify the exact phase of the failure.

Here is a Knowledge Base Article about this tool:

https://support.ruckuswireless.com/articles/000012240

brad303

Hi Bruno, I finally got my hands on a client experiencing the issue. It is on the latest Lenovo/Intel driver Lenovo currently offers (published in October) and the client could see and connect to the SSID.

The article linked just takes me to a contact form but I think I found the Troubleshooting tool you were referencing. I ran the trace while the computer was actively failing, it seems to be failing on the RADIUS authentication and de-authenticating with a failure of "received class 2 frame from non-auth STA". I can also see it repeatedly sending/looping a RADIUS Access Request, challenge, EAP request response loop.

Ruckus Capture.png

cmc4133

Sorry to revive this old thread, but was there ever a reached solution for this issue? Without getting into it, we're having a similar issue on our end that we've yet to figure out, even while working with a Ruckus engineer.

brad303

Unfortunately we have still not found a solution to this issue and are still seeing it. If you find a solution in the end we would definitely be interested.