Xirrus Array Integration Guide Revision Date 0.90 23 April 2010 Copyright © 2009 amigopod Pty Ltd amigopod Headquarters amigopod Pty Ltd Suite 101 349 Pacific Hwy North Sydney, NSW 2060 Australia ABN 74 124 753 421 Web www.amigopod.
Table of Contents Introduction ................................................................................................................................... 3 Test Environment...................................................................................................................... 3 Integration ................................................................................................................................. 5 Xirrus Array Configuration ...........................
Introduction This document outlines the configuration process on both the Xirrus Array and the amigopod appliance to create a fully integrated Visitor Management solution. The solution leverages the captive portal functionality built into the Xirrus Array software image. The Captive portal functionality allows a wireless client to authenticate using a web-based portal. Captive portals are typically used in public access wireless hotspots or for hotel in-room Internet access.
The following table shows the software versions used during the integration testing. This document will be updated in the future if changes in either amigopod or Cisco subsequent releases affect the stability of this integration. It is advised that the customer always check for the latest integration guide available from either amigopod or Cisco. Dated Tested: AmigoPod Version: Plugins Required: Xirrus Array: Integration: April 2010 Kernel2.1, Radius Services 2.1 Standard build only System Software - 4.
Integration Although the Xirrus Array supports both internal and external Captive portal functionality, this integration guide will focus on the later (external) as the internal Captive portal dictates the use of the internal Login Page resident on the Array itself. The Login page is very basic and doesn’t allow for significant customization as is possible with the amigoPod Web Logins feature.
Xirrus Array Configuration The following configuration procedure assumes that the Xirrus Array has been powered up and a basic IP configuration has been applied through the CLI to allow the administrator to access the Web User Interface. The following table again reviews the IP Addressing used in the test environment but this would be replaced with the site specific details of each customer deployment: Xirrus Array Address Internet Gateway Address amigopod IP Address amigopod RADIUS port 192.168.1.104 192.
Step 1 – Create RADIUS Authentication Server Instance In order for the Xirrus Array to successfully authenticate the guest users that will be provisioned on the amigopod appliance, a RADIUS Server needs to be enabled on the Array. From the SecurityGlobal Settings menu option, click the ‘External’ button at the top middle of the screen. Click the Apply CONFIDENTIAL and the Save button (immediately after) to save changes.
Step 2 – Create an SSID and Configure/Enable Web Page Redirect In order for the Xirrus Array to successfully redirect guest users to the web porta hosted by the Amigopod appliance and forward accounting data associated with traffic being generated by guest users, an SSID need to be created and Web Portal Redirect needs to be enabled and configured; along with a RADIUS definition.
Click on the ‘Save’ button (bottom right). Step 3 – RADIUS Configuration To configure the RADUIS Server, uncheck the ‘Global’ box; the SSID Amigopod RADIUS Configuration section should appear. Click the ‘External’ circle and click the ‘Accounting’ box. Enter the IP Address of your Amigopod appliance and the Port Numbers (note, the same IP Address can be used for both the RADIUS and Accounting Servers).
Amigopod Configuration The following configuration procedure assumes that the amigopod software or appliance has been powered up and a basic IP configuration has been applied through the setup wizard to allow the administrator to access the Web User Interface.
Step1 – Create RADIUS NAS for Xirrus Array In order for the Xirrus Array to authenticate users it needs to be able to communicate with the amigopod RADIUS instance. Back in Step 3 of the Xirrus Array configuration, a RADIUS server definition was created. This step configures the amigopod NAS definition for the Xirrus Array. The RADIUS key used in Step 3 needs to be configured exactly the same here for the RADIUS transactions to be successful.
Step 2 – Restart RADIUS Services A restart of the RADIUS Service is required for the new NAS configuration to take affect. Click the Restart RADIUS Server button shown below and wait a few moments for the process to complete.
Step 3 – Configure Xirrus Array Web Logins Page By default the amigopod comes pre-configured with Web Login templates (RADIUS Services Web Logins) for all the major wireless manufactures. The Xirrus template can be modified to suit the local deployment by adding custom HTML code or defined a unique amigopod skin for each captive portal page hosted by the amigopod installed; as shown below: From the RADIUS ServicesWeb Logins page select the Xirrus Login entry and Click the Edit button.
From the RADIUS Web Login page select the Skin that you would like presented as the branding for the Captive Portal page. Modify the sample HTML in the Header HTML, and Login Message section to customize for your local environment. In addition add the following html script to the Footer section: Click the Save Changes button to commit the changes.
Step 3 – Confirm External Captive Portal URL The URL that needs to be configured in the Xirrus Array External Captive Portal section covered in Step 3 can be confirmed by clicking on the test button shown on the screen below under the RADIUS Services Web Logins screen: A Test page will be presented and the URL can be copied from the address bar: CONFIDENTIAL 15
Note: The URL presented in the web browser after the Test button has been clicked will be required in the configuration of the captive portal settings on the Xirrus Array. An example of the URL is shown below: http://192.1668.1.103/xirrusweblogin.php Step 4 – Create a test user account Within the amigopod RADIUS Server a test user account can be created using the amigopod Guest Manager. From the Guest Manager menu, select the Create New Guest Account option.
Testing the Configuration Now that the configuration of both the Xirrus Array and the amigopod appliance is complete, the following steps can be followed to verify the configuration. Step 1 - Connect to the amigopod wireless network Using a test laptop with a compatible 802.11 based wireless card attempt to connect to the advertised amigopod wireless network. The screen capture below shows the interface used on a Windows XP SP2 based laptop.
Step 2 – Confirm DHCP IP Address received Using the Windows Command Prompt or equivalent in the chosen operating system, confirm that a valid IP Address has been received from the DHCP server defined on the Xirrus Array. Issue the ipconfig command from the Windows Command Prompt to display the IP information received from the DHCP process. As illustrated below on the Wireless adapter an IP Address of 192.168.1.101 has been received.
Step 3 – Launch Web Browser and login When the web browser on the test laptop is launched the Xirrus Array will automatically capture the session and redirect the user to the amigopod hosted login page as shown below: Enter the test user details created in Step 3 of the amigopod configuration procedure and click the Login button. At this point the test user should be successfully authenticated and allowed to transit through the Array and onto the Internet or Corporate network.
Step 4 – Confirm RADIUS debug messages on amigopod Once the test laptop has successfully authenticated and now able to browse the Internet, an entry should appear in the RADIUS logs confirming the positive authentication of the test user – in this example, jsmith@abc.om Select the RADIUS ServicesServer Control menu option and the following screen should be displayed showing the status of the RADIUS server and a tail of the log file, including an entry for the positive authentication transaction.
