Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
radius:rad_overview [2024/02/12 04:54] systemradius:rad_overview [2024/02/13 15:21] (current) – [Edit - Panel] system
Line 11: Line 11:
  
 ====== Components of the RADIUS server ====== ====== Components of the RADIUS server ======
-<panel type="default">+<panel type="primary">
 {{:radius:radius_overview.png|}} {{:radius:radius_overview.png|}}
 </panel> </panel>
Line 30: Line 30:
  
 ===== RADIUS Profile (Authorization) ===== ===== 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) ===== ===== 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. +  * realm name can therefore play a role in forwarding RADIUS traffic to other RADIUS servers.
  
  
  • radius/rad_overview.1707706491.txt.gz
  • Last modified: 2024/02/12 04:54
  • by system