This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
rduserguide [2016/05/06 21:10] – created admin | rduserguide [2016/08/15 21:57] (current) – admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== RADIUSdesk | + | ====== |
- | Consider the following diagram: | + | |
- | {{: | + | |
- | Let us briefly describe each of the items inside the diagram and how they relate to each other. | + | <WRAP center round box 100%> |
- | ===== Access Provider | + | ===== Overview of RADIUSdesk components |
- | * The root user of RADIUSdesk | + | |
- | * Each access provider can manage their own little playpen. | + | * [[ technical_discussions: |
- | * The playpen consists of various components which will be discussed next. | + | |
+ | | ||
+ | * [[ technical_discussions: | ||
+ | * [[ technical_discussions: | ||
+ | * [[ technical_discussions: | ||
+ | * [[ technical_discussions: | ||
+ | * [[user_guide: | ||
+ | * [[user_guide: | ||
+ | </ | ||
- | ===== Realms ===== | ||
- | * Realms are a way to group Vouchers, Permanent Users and Devices. | ||
- | * Each Voucher, Permanent User or Device has to belong to a single **Realm**. | ||
- | |||
- | ===== Vouchers ===== | ||
- | * Vouchers are disposable and mass produced ways to provide Internet Access. | ||
- | * A Voucher system does not care who the person that uses the voucher is. | ||
- | |||
- | ===== Permanent Users ===== | ||
- | * Permanent Users are used for long term usage with options to give a person a monthly usage cap. | ||
- | * Permanent users typically have one or more devices which they own. This is managed through the BYOD Manager. | ||
- | |||
- | ===== Devices ===== | ||
- | * Devices are a sub-item to Permanent Users. | ||
- | * Each device registered on RADIUSdesk has to belong to a Permanent User. | ||
- | * The Device will also by association belong to the same realm to which its owner belongs. | ||
- | |||
- | ===== Profiles ===== | ||
- | * Each Voucher, Permanent User and Device also has to be assigned to a single **Profile**. | ||
- | * A Profile typically controls the connection of a user, determining how much data or bandwidth the User, Voucher or Device is allowed. | ||
- | * Each Profile in turn can consist of zero or more Profile Components. | ||
- | |||
- | ==== Profile Components ==== | ||
- | * Profile Components are the building blocks to create flexible profiles. | ||
- | * Apart from bandwidth and data usage, you can add fields like Time or Expiry Date to a profile. | ||
- | |||
- | ===== NAS devices ===== | ||
- | * NAS (Network Access Server) devices are network equipment that provides a controlled way to grant users access to the network. | ||
- | * A WiFi Access Point with a captive portal (like CoovaChilli or Mikrotik) are examples of NAS devices. | ||
- | |||
- | ==== NAS device tags ==== | ||
- | * Each NAS Device can have zero or more tags to help group and label Access Points. | ||
- | |||
- | ===== Dynamic Login Pages ===== | ||
- | * Dynamic Login Pages are the custom welcoming page when users connect to the Hotspot. | ||
- | * You can create a login page with custom user fields, themes and graphics. | ||
- | * Dynamic Login Pages provides an easy and central way to manage login pages for CoovaChilli and Mikrotik Captive Portals. | ||
- | |||
- | ===== MESHdesk ===== | ||
- | * MESHdesk is the interface that allows you to add and manage NAS devices in an automated way. This is most useful in a mesh environment. | ||
- | * MESHdesk provides an easy and central way to manage and monitor Batman-adv mesh networks. | ||