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_kick [2024/02/13 04:38] – [Mikrotik] systemradius:rad_kick [2024/02/13 04:47] (current) – system
Line 1: Line 1:
 +<nav type="pills" justified="false">
 +  * [[:user_manuals|Back to Documentation]]
 +  * [[:radius:rad_kick|Disconnecting Active RADIUS Users]]
 +</nav>
 +
 +-----
 +
 ====== Disconnecting Active RADIUS Users ====== ====== Disconnecting Active RADIUS Users ======
 ===== Introduction ===== ===== Introduction =====
Line 54: Line 61:
  
 ===== Add Support for additional types ===== ===== Add Support for additional types =====
-  * This section is a technical section for those who wants to introduce new RADIUS Client types. +  * This section is a technical section for those who want to introduce new RADIUS client types. 
-  * The list in the drop-down is specified in the following file: ///var/www/rdcore/cake4/rd_cake/config/RadiusDesk.php//+  * The list in the drop-down list is specified in the following file: ///var/www/rdcore/cake4/rd_cake/config/RadiusDesk.php//
 <code php> <code php>
 //Define nas types //Define nas types
Line 62: Line 69:
 $config['nas_types'][2]     = ['name' => 'Mikrotik-API', 'id' => 'Mikrotik-API',    'active' => true]; $config['nas_types'][2]     = ['name' => 'Mikrotik-API', 'id' => 'Mikrotik-API',    'active' => true];
 </code> </code>
-  * Then when selecting an active user in **Activity Monitor** to disconnect behind the scenes the code will determine the type of RADIUS  Client based on the **nasidentifier** field. (This is in the radacct table and has to match the value in the dynamic-clients table) +  * If you then select an active user in **Activity Monitor** to disconnect behind the scenes, the code determines the type of RADIUS client based on the **nasidentifier** field.  (This field is located in the radacct table and must match the value in the dynamic-clients table) 
-  * This all happens inside the ///var/www/rdcore/cake4/rd_cake/src/Controller/Component/KickerComponent.php// file. +  * This is all done within the file ///var/www/rdcore/cake4/rd_cake/src/Controller/Component/KickerComponent.php//. 
-  * Thus adding support for additional types will involve adding additional sections to the PHP code. +  * So if you want to add support for more types, you will need to add additional sections to the PHP code. 
-  * See the snippet below.+  * Take a look at the following snippet.
 <code php> <code php>
-//First we try to locate the client under dynamic_clients+//First we try to find the client under dynamic_clients
 $dc = $this->DynamicClients->find() $dc = $this->DynamicClients->find()
  ->where(['DynamicClients.nasidentifier' => $nasidentifier])  ->where(['DynamicClients.nasidentifier' => $nasidentifier])
Line 91: Line 98:
  
 </code> </code>
-  * That's the only things involved in disconnecting an active RADIUS user. +  * This is the only thing required to disconnect an active RADIUS user. 
-  * The FUP implementation also utilizes this mechanism so this also serve as a core component for the FUP implementation to be successful.+  * The FUP implementation also uses this mechanism, so this is also a core component for the success of the FUP implementation.
  
  • radius/rad_kick.1707791927.txt.gz
  • Last modified: 2024/02/13 04:38
  • by system