Differences

This shows you the differences between two versions of the page.

--- radius:rad_overview [2024/02/11 20:47] – [RADIUS User (Authentication)] system
+++ radius:rad_overview [2024/02/13 15:21] (current) – [Edit - Panel] system
@@ Line 6: / Line 6: @@
 -----
-  * RADIUSdesk is a modern front-end to FreeRADIUS.
+  * RADIUSdesk is a modern frontend for FreeRADIUS.
-  * This page will serve as an overview.
+  *  This page is intended to give you an overview.
-  * The components are then discussed in more depth in their own dedicated pages.
+  * The components are described in more detail on their own pages.
 ====== Components of the RADIUS server ======
+<panel type="primary">
-  * When a RADIUS client contacts RADIUSdesk the following components will be involved.
+{{:radius:radius_overview.png|}}
+</panel>
+  * When a RADIUS client contacts RADIUSdesk, the following components are involved.
 ===== RADIUS Client =====
-  * RADIUS Clients have to be defined and added to the list of RADIUS clients that are allowed to be processed by RADIUSdesk.
+  * RADIUS clients must be defined and added to the list of RADIUS clients that RADIUSdesk is allowed to process.
-  * We use a server wide common shared secret and then identify a RADIUS Client based on the **Nas-Identifier** attribute in the RADIUS request.
+  * We use a server-wide shared secret and then identify a RADIUS client using the Nas-Identifier attribute in the RADIUS request.
-  * This allows the server to process requests even if the incoming IP Address of the client changes.
+  * This allows the server to process requests even if the incoming IP address of the client changes.
 ===== RADIUS User (Authentication) =====
-  * RADIUS Authentication request will contain a username.
+  * The RADIUS authentication request contains a user name.
-  * RADIUSdesk features the following user types
+  *  RADIUSdesk offers the following user types
         * Permanent Users
         * Vouchers
         * BYOD
-  * For the Authentication to succeed, the username in the authentication request <wrap em>must match</wrap> one of the users defined in RADIUSdesk.
+  * For authentication to be successful, the user name in the authentication request <wrap em>must match</wrap> one of the users defined in RADIUSdesk.
 ===== RADIUS Profile (Authorization) =====
-  * Each RADIUS user has to belong to a RADIUS profile.
+  * Every RADIUS user must belong to a RADIUS profile.
-  * This profile will typically determine the service that the user will be assigned when they connect to the network.
+  * This profile usually determines the service that is assigned to the user when they connect to the network.
-  * The profile can for instance specify the bandwidth assigned to a PPPoE user.
+  *  For example, the profile can define the bandwidth that is assigned to a PPPoE user.
 ===== RADIUS Realm (Grouping) =====
-  * Each RADIUS user also has to belong to a RADIUS Realm.
+  * Each RADIUS user must also belong to a RADIUS realm.
-  * Realms are a method used to group users together and may also used to determine if a RADIUS request have to be forwarded to another RADIUS server to process the request.
+  * Realms are a method of grouping users and can also be used to determine whether a RADIUS request must be forwarded to another RADIUS server in order to process the request.
-  * So a realm name might be detrimental in the routing of RADIUS traffic to other RADIUS servers.
+  * A realm name can therefore play a role in forwarding RADIUS traffic to other RADIUS servers.