AG 2100Introduction 19RADIUS-Driven Auto ConfigurationNomadix’ unique Remote Authentication Dial-In User Service (RADIUS)-driven AutoConfiguration functionality utilizes the existing infrastructure of a mobile operator to providean effortless and rapid method for configuring devices for fast network roll-outs. Onceconfigured, this methodology can also be effectively used to centrally manage configurationprofiles for all Nomadix devices in the public access network.Two subsequent events drive the automatic configuration of Nomadix devices:z A flow of RADIUS Authentication Request and Reply messages between theNomadix gateway and the centralized RADIUS server that specify the metaconfiguration file location (containing a listing of individual configuration files andtheir download frequency status) are downloaded from an FTP server into the flash ofthe Nomadix device.z Defines the automated login into the centralized FTP server and the actual downloadprocess into the flash.Optionally, the RADIUS authentication process and FTP download can be secured by sendingtraffic through a peer-to-peer IPSec tunnel established by the Nomadix gateway andterminated at the NOC (Network Operations Center). See also, “Secure Management” onpage 21.RADIUS ClientNomadix offers an integrated RADIUS client with the NSE, allowing service providers totrack or bill users based on number of connections, connection location, bytes sent andreceived, connect time, etc. The customer database can exist in a central RADIUS server,along with associated attributes for each user. When a customer connects into the network, theRADIUS client authenticates the customer with the RADIUS server, applies associatedattributes stored in that customer's profile, and logs their activity (including bytes transferred,connect time, etc.). The NSE's RADIUS implementation also handles vendor specificattributes (VSAs), required by WISPs that want to enable more advanced services and billingschemes, such as a per device/per month connectivity fees. See also, “RADIUS-Driven AutoConfiguration” on page 19.
