AG 3100Introduction 17RADIUS-driven Auto ConfigurationNomadix’ unique RADIUS-driven Auto Configuration functionality utilizes the existinginfrastructure of a mobile operator to provide an effortless and rapid method for configuringdevices for fast network roll-outs. Once configured, this methodology can also be effectivelyused to centrally manage configuration profiles for all Nomadix devices in the public accessnetwork.Two subsequent events drive the automatic configuration of Nomadix devices:1. A flow of RADIUS Authentication Request and Reply messages between the Nomadixgateway and the centralized RADIUS server that specifies the location of the metaconfiguration file (containing a listing of the individual configuration files and theirdownload frequency status) are downloaded from an FTP server into the flash of theNomadix device.2. 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 sendingthe traffic through a peer-to-peer IPSec tunnel established by the Nomadix gateway andterminated at the NOC (Network Operations Center). See also, Secure Management on page19.RADIUS ClientNomadix offers an integrated RADIUS (Remote Authentication Dial-In User Service) clientwith the NSE allowing service providers to track or bill users based on the number ofconnections, location of the connection, bytes sent and received, connect time, etc. Thecustomer database can exist in a central RADIUS server, along with associated attributes foreach user. When a customer connects into the network, the RADIUS client authenticates thecustomer with the RADIUS server, applies associated attributes stored in that customer'sprofile, and logs their activity (including bytes transferred, connect time, etc.). The NSE'sRADIUS implementation also handles vendor specific attributes (VSAs), required by WISPsthat want to enable more advanced services and billing schemes, such as a per device/permonth connectivity fee. See also, RADIUS Proxy on page 18.
