Differences

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

Link to this comparison view

Both sides previous revision Previous revision
smradiusd.conf [2013-12-06 14:58] – Fix formatting rspencersmradiusd.conf [2016-09-27 08:33] (current) nkukard
Line 1: Line 1:
 ====== smradiusd.conf ====== ====== smradiusd.conf ======
  
-===== [server] =====+====== [server] ======
  
-==== user ====+===== user =====
  
 User to run this daemon as: User to run this daemon as:
Line 11: Line 11:
 </code> </code>
  
-==== group ====+===== group =====
  
 <code> <code>
Line 17: Line 17:
 </code> </code>
  
-==== pid_file ====+===== pid_file =====
  
 Filename to store pid of parent process: Filename to store pid of parent process:
Line 25: Line 25:
 </code> </code>
  
-==== cache_file ====+===== cache_file =====
  
 File name to store cache: File name to store cache:
Line 33: Line 33:
 </code> </code>
  
-==== background ====+==== background =====
  
 Prevent smradiusd from going into the background: Prevent smradiusd from going into the background:
Line 41: Line 41:
 </code> </code>
  
-==== Preforking configuration ====+===== Preforking configuration =====
  
   * min_server - Minimum servers to keep around   * min_server - Minimum servers to keep around
Line 61: Line 61:
 </code> </code>
  
-==== log_level ====+===== log_level =====
  
 Specify the level of logging to use when smradius is running: Specify the level of logging to use when smradius is running:
Line 75: Line 75:
 </code> </code>
  
-==== log_file ====+===== log_file =====
  
 File to log to instead of stdout: File to log to instead of stdout:
Line 83: Line 83:
 </code> </code>
  
-==== log_detail ====+===== log_detail =====
  
 Things to log in extreme detail: Things to log in extreme detail:
Line 95: Line 95:
 </code> </code>
  
-==== host ====+===== host =====
  
 IP to listen on, * for all: IP to listen on, * for all:
Line 103: Line 103:
 </code> </code>
  
-==== timeout ====+===== timeout =====
  
 Timeout in communication with clients: Timeout in communication with clients:
Line 111: Line 111:
 </code> </code>
  
-==== cidr_allow/cidr_deny ====+===== cidr_allow/cidr_deny =====
  
 Comma, whitespace or semi-colon separated. Contains a CIDR block to compare the clients IP to. If cidr_allow or cidr_deny options are given, the incoming client must match a cidr_allow and not match a cidr_deny or the client connection will be closed. Comma, whitespace or semi-colon separated. Contains a CIDR block to compare the clients IP to. If cidr_allow or cidr_deny options are given, the incoming client must match a cidr_allow and not match a cidr_deny or the client connection will be closed.
Line 120: Line 120:
 </code> </code>
  
-==== event_timezone ====+===== event_timezone =====
  
 Event timestamp timezone, in "Continent/City" format, defaults to "GMT": Event timestamp timezone, in "Continent/City" format, defaults to "GMT":
Line 128: Line 128:
 </code> </code>
  
-===== [radius] =====+====== [radius] ======
  
-==== use_packet_timestamp ====+===== use_packet_timestamp =====
  
 Use packet timestamp, if unset, the default is to use the server timestamp at the moment the packet is received, default is "no". Use packet timestamp, if unset, the default is to use the server timestamp at the moment the packet is received, default is "no".
- 
-=== WARNING!!!! === 
  
 Not all routers keep time, it may occur that some routers depend on getting date & time apon reboot from an ntp server. The problem will arise when the router cannot get the date and time before the first user logs in resulting in sessions with a period key in the current month but an event timestamp in 1970. Not all routers keep time, it may occur that some routers depend on getting date & time apon reboot from an ntp server. The problem will arise when the router cannot get the date and time before the first user logs in resulting in sessions with a period key in the current month but an event timestamp in 1970.
Line 142: Line 140:
 </code> </code>
  
-==== use_abuse_prevention ====+===== use_abuse_prevention =====
  
 Radius server abuse prevention. Radius server abuse prevention.
Line 152: Line 150:
 </code> </code>
  
-==== access_request_abuse_threshold ====+===== access_request_abuse_threshold =====
  
 How fast can a NAS spam the same type of request: How fast can a NAS spam the same type of request:
Line 161: Line 159:
   * <code>accounting_request_abuse_threshold=5</code>   * <code>accounting_request_abuse_threshold=5</code>
  
-===== [database] =====+====== [database] ======
  
-==== Database connection details ====+===== DSN/Username/Password =====
  
 <code> <code>
Line 172: Line 170:
 </code> </code>
  
-==== bypass_mode ====+===== bypass_mode =====
  
 What do we do when we have a database connection problem: What do we do when we have a database connection problem:
Line 183: Line 181:
 </code> </code>
  
-==== bypass_timeout ====+===== bypass_timeout =====
  
 How many seconds before retrying a DB connection: How many seconds before retrying a DB connection:
Line 191: Line 189:
 </code> </code>
  
-==== accounting_usage_cache_time ====+===== accounting_usage_cache_time =====
  
 How long to cache the usage query for, default is "300" (seconds). You can use  "no", "0", "false"  to disable, specify a number > 1, or use "yes", "1", "true" to enable with the default value. How long to cache the usage query for, default is "300" (seconds). You can use  "no", "0", "false"  to disable, specify a number > 1, or use "yes", "1", "true" to enable with the default value.
Line 199: Line 197:
 </code> </code>
  
-==== userdb_data_cache_time ====+===== userdb_data_cache_time =====
  
 How long to cache the data query for default is "300" (seconds). You can use  "no", "0", "false"  to disable, specify a number > 1, or use "yes", "1", "true" to enable with the default value. How long to cache the data query for default is "300" (seconds). You can use  "no", "0", "false"  to disable, specify a number > 1, or use "yes", "1", "true" to enable with the default value.