ºÚÁϺ£½Ç91Èë¿Ú

This document is meant to be used in conjunction with RADIUS Configuration and Authentication.

ºÚÁϺ£½Ç91Èë¿Ú has updated the RADIUS infrastructure, which required changing IP addresses used for this application. The current list (below) should be used for all RADIUS applications and/or devices. Make sure to update any application and/or device using RADIUS with the IPs listed on this page.

Prerequisites:

• Device or service endpoint that supports RADIUS and either EAP-TTLS/PAP or EAP-PEAP/MSCHAPv2 authentication methods.  Simple PAP may also be used, but we highly recommend you use a more secure authentication protocol such as EAP-TTLS/PAP or EAP-PEAP/MSCHAPv2
• Port 1812/UDP to our RADIUS service endpoints (RADIUS Accounting on 1813 is not supported)
• The ºÚÁϺ£½Ç91Èë¿Ú RADIUS server certificate (For EAP-TTLS implementations)
• The Shared Secret from the ºÚÁϺ£½Ç91Èë¿Ú RADIUS Server configuration

Configuration

The following is general information for setting up RADIUS on a device or service endpoint. Please refer to your vendor's documentation for specific configuration details, or for a specific example, see Configure a Cisco Meraki WAP to Use Cloud RADIUS.

ºÚÁϺ£½Ç91Èë¿Ú RADIUS server details:

When configuring your application or device, choose the IP(s) closest to your geographic location.

Encryption/Authentication Mode:

• WPA2 Enterprise
• WPA2 with RADIUS

Testing the connection:

• Authenticate using the ºÚÁϺ£½Ç91Èë¿Ú username and password, or email address and password.
• Test the authentication directly from the device (If supported)

Tips for Debugging Radius:

• Troubleshooting Radius Server Authentication