A. Each AP needs to be a RADIUS client.
B. Non-proxy requires a unique shared secret.
C. Non-proxy only works with 802.1X authentication.
D. Non-proxy authentication requires use of standard ports.
Explanation:
In non-proxy RADIUS mode, the SmartZone controller does not act as an intermediary for authentication requests. Instead, each access point (AP) communicates directly with the RADIUS server for client authentication.
According to RUCKUS One Online Help C WLAN Authentication Modes (Proxy vs Non-Proxy), the key requirement is that each AP must be defined as a RADIUS client in the RADIUS server configuration. If not, authentication requests from the APs are rejected because the server does not recognize their source IPs or shared secrets.
This behavior differs from proxy mode, where only the SmartZone controller needs to be added as a RADIUS client. Port numbers (1812/1813) and encryption types remain standard, and both 802.1X and MAC authentication are supported.
Therefore, authentication failure in this scenario occurs because each AP must be authorized individually in the RADIUS server when non-proxy mode is used.
Reference: RUCKUS One Online Help C Proxy and Non-Proxy RADIUS Authentication Configuration RUCKUS Analytics 3.5 User Guide C Authentication Log Analysis and Proxy Modes RUCKUS AI Documentation C WLAN AAA Communication Paths and RADIUS Modes