Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
smradiusd.conf [2013-12-06 14:58] – Fix formatting rspencer | smradiusd.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: | ||
</ | </ | ||
- | ==== group ==== | + | ===== group ===== |
< | < | ||
Line 17: | Line 17: | ||
</ | </ | ||
- | ==== pid_file ==== | + | ===== pid_file |
Filename to store pid of parent process: | Filename to store pid of parent process: | ||
Line 25: | Line 25: | ||
</ | </ | ||
- | ==== cache_file ==== | + | ===== cache_file |
File name to store cache: | File name to store cache: | ||
Line 33: | Line 33: | ||
</ | </ | ||
- | ==== background ==== | + | ==== background |
Prevent smradiusd from going into the background: | Prevent smradiusd from going into the background: | ||
Line 41: | Line 41: | ||
</ | </ | ||
- | ==== Preforking configuration ==== | + | ===== Preforking configuration |
* min_server - Minimum servers to keep around | * min_server - Minimum servers to keep around | ||
Line 61: | Line 61: | ||
</ | </ | ||
- | ==== 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: | ||
</ | </ | ||
- | ==== log_file ==== | + | ===== log_file |
File to log to instead of stdout: | File to log to instead of stdout: | ||
Line 83: | Line 83: | ||
</ | </ | ||
- | ==== log_detail ==== | + | ===== log_detail |
Things to log in extreme detail: | Things to log in extreme detail: | ||
Line 95: | Line 95: | ||
</ | </ | ||
- | ==== host ==== | + | ===== host ===== |
IP to listen on, * for all: | IP to listen on, * for all: | ||
Line 103: | Line 103: | ||
</ | </ | ||
- | ==== timeout ==== | + | ===== timeout |
Timeout in communication with clients: | Timeout in communication with clients: | ||
Line 111: | Line 111: | ||
</ | </ | ||
- | ==== cidr_allow/ | + | ===== cidr_allow/ |
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: | ||
</ | </ | ||
- | ==== event_timezone ==== | + | ===== event_timezone |
Event timestamp timezone, in " | Event timestamp timezone, in " | ||
Line 128: | Line 128: | ||
</ | </ | ||
- | ===== [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 " | Use packet timestamp, if unset, the default is to use the server timestamp at the moment the packet is received, default is " | ||
- | |||
- | === 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: | ||
</ | </ | ||
- | ==== use_abuse_prevention ==== | + | ===== use_abuse_prevention |
Radius server abuse prevention. | Radius server abuse prevention. | ||
Line 152: | Line 150: | ||
</ | </ | ||
- | ==== 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: | ||
* < | * < | ||
- | ===== [database] ===== | + | ====== [database] |
- | ==== Database connection details | + | ===== DSN/ |
< | < | ||
Line 172: | Line 170: | ||
</ | </ | ||
- | ==== 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: | ||
</ | </ | ||
- | ==== bypass_timeout ==== | + | ===== bypass_timeout |
How many seconds before retrying a DB connection: | How many seconds before retrying a DB connection: | ||
Line 191: | Line 189: | ||
</ | </ | ||
- | ==== accounting_usage_cache_time ==== | + | ===== accounting_usage_cache_time |
How long to cache the usage query for, default is " | How long to cache the usage query for, default is " | ||
Line 199: | Line 197: | ||
</ | </ | ||
- | ==== userdb_data_cache_time ==== | + | ===== userdb_data_cache_time |
How long to cache the data query for default is " | How long to cache the data query for default is " |