rlm_always(5) FreeRADIUS Module rlm_always(5)NAME
rlm_always - FreeRADIUS Module
DESCRIPTION
The rlm_always module provides a simple way to "always" return a value during the processing of a configuration section. The module does
nothing other than return a configured value.
The main configuration item to be aware of is:
rcode This module will always return with the rcode specified. The default, if none specified is: fail (RLM_MODULE_FAIL).
The valid options are:
reject RLM_MODULE_REJECT
fail RLM_MODULE_FAIL
ok RLM_MODULE_OK
handled
RLM_MODULE_HANDLED
invalid
RLM_MODULE_INVALID
userlock
RLM_MODULE_USERLOCK
notfound
RLM_MODULE_NOTFOUND
noop RLM_MODULE_NOOP
updated
RLM_MODULE_UPDATED
CONFIGURATION
modules {
...
always ok {
rcode = ok
}
...
}
...
authorize {
...
redundant {
sql1 # try to find the user in sql1
sql2 # try to find the user in sql2
ok # if still not found, it's OK.
}
...
}
SECTIONS
authorization, authentication, postauthentication, preaccounting, accounting, preproxy, postproxy
FILES
/etc/raddb/radiusd.conf
SEE ALSO radiusd(8), radiusd.conf(5)AUTHOR
Chris Parker, cparker@segv.org
3 February 2004 rlm_always(5)
Check Out this Related Man Page
rlm_detail(5) FreeRADIUS Module rlm_detail(5)NAME
rlm_detail - FreeRADIUS Module
DESCRIPTION
The rlm_detail module writes radius packets to 'detail' files. It is primarily used for storing accounting information, but can be used in
other sections to write packet details as well.
The file format is similar to that of the old Livingston servers, and many 'detail' file parsers should work with FreeRADIUS.
The main configuration items to be aware of are:
file The file name in which to store the radius packet records. NOTE: this variable is run through dynamic string expansion, and can
include FreeRADIUS variables to create a dynamic filename.
%{radacctdir}/%{Client-IP-Address}/detail-%Y%m
This will create one file per month, for each client.
This accomplishes 'file rotation' automatically from
within the server.
perm The file permissions of the file. If omitted, the default is 0600.
dirperm
The directory permissions of the directory where the detail files are created. The default is 0755.
locking
This option is set to 'yes' or 'no'. By default it is 'no'. Set this to yes to enable file locking, which is used with the
'radrelay' program.
CONFIGURATION
modules {
...
detail {
filename = %A/%{Client-IP-Address}/detail-%Y%m
permissions = 0600
dir_permissions = 0755
locking = no
}
...
}
...
accounting {
...
detail
...
}
SECTIONS
authorization, accounting, pre_proxy, post_proxy, post_authentication
FILES
/etc/raddb/radiusd.conf
SEE ALSO radiusd(8), radiusd.conf(5)AUTHORS
Chris Parker, cparker@segv.org
27 June 2013 rlm_detail(5)
I could use some help with freeradius configuration. If there is any expert user out there kind enough to give me a hand, would really appreciate it.
Goal:
We are trying to use the freeRADIUS server's VMPS integration feature. Unfortunately the wiki pages do not have real life deployment... (0 Replies)
Hi,
I have my informix queries in files named sql1.sql and sql2.sql.
I am executing these queries in a remote informix db server.The data got as a result of executing sql1.sql and sql2.sql is got in file1.dat and file2.dat respectively.
cmd= ssh "$USER_NAME"@"$HOST_NAME" "export... (0 Replies)