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
Last revisionBoth sides next revision
usage [2016-09-19 17:16] wikiadminusage [2016-09-19 17:32] – [SMRadius-Disable-WebUITopup] wikiadmin
Line 50: Line 50:
   * [[mod_feature_capping.pm|SMRadius-AutoTopup-Uptime-Notify]]   * [[mod_feature_capping.pm|SMRadius-AutoTopup-Uptime-Notify]]
   * [[mod_feature_capping.pm|SMRadius-AutoTopup-Uptime-NotifyTemplate]]   * [[mod_feature_capping.pm|SMRadius-AutoTopup-Uptime-NotifyTemplate]]
-  * +
 ===== Validity ==== ===== Validity ====
  
Line 67: Line 67:
 ====== Core ====== ====== Core ======
  
-  * __SMRadius-Username-Transform__ +===== SMRadius-Evaluate ===== 
-    * Transforms a username from the supplied username to the configured username (Currently disabled) +Evaluate and set an attribute / attributes based on the results of the evaluation. Syntax: TEST CASE ? TRUE_ATTRIBUTE : FALSE. 
-    <code># Transfrom user@example.net to user@this.example.net + 
-SMRadius-Username-Transform  :=  example.net=this.example.net</code>+Lets take a real life example: 
 + 
 +1. For traffic under 80000Mbyte, we set an attribute 
 +<code> 
 +SMRadius-Evaluate ||+= SMRadius_Capping_TotalDataUsage < 80000 ? [14988:Mikrotik-Rate-Limit] = 1m/4m 1m/6m 1m/5m 10/10 1 
 +</code> 
 + 
 +2For traffic above 80000Mbyte, but below 130000Mbyte, we set the same attribute to something else... 
 +<code> 
 +SMRadius-Evaluate ||+= SMRadius_Capping_TotalDataUsage > 80000 && SMRadius_Capping_TotalDataUsage < 130000 ? [14988:Mikrotik-Rate-Limit] 512k/1m 640k/2m 640k/2m 10/10 4 
 +</code> 
 + 
 +3For traffic above 130000Mbyte, we set the traffic to a third different value... 
 +<code> 
 +SMRadius-Evaluate ||+SMRadius_Capping_TotalDataUsage > 130000 ? [14988:Mikrotik-Rate-Limit] = 128k/384k 512k/1024k 256k/512k 10/10 8 
 +</code> 
 + 
 +===== SMRadius-Peer-Address ===== 
 + 
 +Allows the admin to specify an address that the peer address must match in order to be authorizedThe user / group attribute SMRadius-Peer-Address will be checked against the peer address of the client device. 
 + 
 +<code> 
 +SMRadius-Peer-Address  ==  <peer address> 
 +</code> 
 + 
 +===== SMRadius-Disable-WebUITopup ===== 
 + 
 +Allows one to build web ui's that ignore topups, this attribute is not used internally. 
 + 
 +===== SMRadius-Username-Transform =====
  
-  * __SMRadius-Evaluate__ +<btn type="warning" size="xs">Work in Progress</btn>
-    * Evaluate and set an attribute attributes based on the results of the evaluation. Syntax: TEST CASE ? TRUE_ATTRIBUTE : FALSE+
  
-  * __SMRadius-Peer-Address__ +Transforms a username from the supplied username to the configured username.
-    * Allows the admin to specify an address that the peer address must match in order to be authorized. The user / group attribute SMRadius-Peer-Address will be checked against the peer address of the client device. +
-    * <code>SMRadius-Peer-Address  ==  < peer-address ></code>+
  
-  * __SMRadius-Disable-WebUITopup__ +<code> 
-    * Allows one to build web ui's that ignore topups, this attribute is not used internally at all.+# Transfrom user@example.net to user@this.example.net 
 +SMRadius-Username-Transform  :=  example.net=this.example.net 
 +</code>