Seth Woolley's Man Viewer

Manual for radiusd - man 8 radiusd

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

RADIUSD(8)                     FreeRADIUS Daemon                    RADIUSD(8)

       radiusd(5,8) - Authentication, Authorization and Accounting server

       radiusd(5,8) [-A] [-S] [-a accounting_directory] [-b] [-c] [-d config_direc-
       tory] [-f] [-i ip-address] [-l log_directory] [-g facility]  [-p  port]
       [-s] [-v] [-x] [-X] [-y] [-z]

       This  is  the FreeRADIUS implementation of the well known radius server
       program.  Even though this program  is  largely  compatible  with  Liv-
       ingston's radius version(1,3,5) 2.0, it is not based on any part of that code.

       FreeRADIUS is a high-performance and highly configurable RADIUS server.
       As  a  result, it can be difficult to configure in(1,8) systems with complex
       requirements.  Our suggestion is to proceed via the following steps:

       1) Always run the server in(1,8) debugging mode ( radiusd(5,8) -X ).   We  cannot
       emphasize  this enough.  If you are not running the server in(1,8) debugging
       mode, you will not be able to see what is doing, and you  will  not  be
       able to correct any problems.

       2)  When  editing  the radiusd.conf file(1,n), change as little as possible,
       especially in(1,8) the authorize{} section.  The ordering of the modules  is
       critical for the server to be able to "automatically" figure out how to
       handle the request.  Changing the order of the modules ensures that the
       server will not work.

       3)  When  testing,  start off by configuring a user and password in(1,8) the
       users(1,5) file.  So long as the server knows about a user, and has a clear-
       text  password  for that user, almost all of the authentication methods
       will "just work".

       4) Gradually add more complex configurations to the server, while test-
       ing  them  as  you go.  If you start off by configuring the server in(1,8) a
       complex configuration, you will never be able to debug it.

       5) Ask questions on the  mailing  list  (freeradius-users@lists.freera-   When  asking  questions, include the output from debugging
       mode ( radiusd(5,8) -X ).  This information will allow people to  help  you.
       Without it, your message will get ignored.

       RADIUS  is  a  protocol  spoken  between  an access(2,5) server, typically a
       device connected to several modems or ISDN lines, and a radius  server.
       When  a user connects to the access(2,5) server, (s)he is asked for a login-
       name and a password. This  information  is  then  sent  to  the  radius
       server. The server replies with "access(2,5) denied", or "access(2,5) OK". In the
       latter case login(1,3,5) information is sent along, such as the IP address  in(1,8)
       the case of a PPP connection.

       The  access(2,5)  server  also  sends login(1,3,5) and logout records to the radius
       server so accounting can be done. These records are kept for each  ter-
       minal  server  seperately in(1,8) a file(1,n) called detail, and in(1,8) the wtmp com-
       patible logfile /var/log/radwtmp.

       -A     Write a file(1,n) detail.auth in(1,8) addition to the standard detail file(1,n)
              in(1,8)  the same directory. This file(1,n) will contain all the authenti-
              cation-request records. This can be useful  for  debugging,  but
              not for normal operation.

              This command line option is accepted only for backwards compati-
              bility.  It no longer does anything.  See the configuration  for
              the detail module in(1,8) radiusd.conf.

       -S     Write  the  stripped usernames (without prefix or suffix) in(1,8) the
              detail file(1,n) instead of the raw(3x,7,8,3x cbreak) record as received from the  ter-
              minal server.

              This    command    line   option   is   deprecated.    See   the
              log_stripped_names configuration item in(1,8) the radiusd.conf  file.

       -a accounting directory
              This  defaults  to  /var/log/radacct.  If that directory exists,
              radiusd(5,8) will write(1,2) an ascii(1,7) accounting record into a detail file(1,n)
              for every login(1,3,5)/logout recorded. The location of the detail file(1,n)
              is acct_dir/terminal_server/detail.

              This command line option is deprecated.  See the radacctdir con-
              figuration item in(1,8) the radiusd.conf file.

       -l logging directory
              This  defaults to /var/log. Radiusd writes a logfile here called
              radius.log. It contains informational and  error(8,n)  messages,  and
              optionally  a record of every login(1,3,5) attempt (for aiding an ISP's
              helpdesk). The special arguments stdout  and  stderr  cause  the
              information  to  get written to the standard output, or standard
              error(8,n) instead. The special argument syslog(2,3,5,3 Sys::Syslog) sends the information
              with syslog(2,3,5,3 Sys::Syslog)(3).

              This command line option is deprecated.  See the log_dir config-
              uration item in(1,8) the radiusd.conf file.

       -g facility
              Specifies the syslog(2,3,5,3 Sys::Syslog) facility to be used with -l syslog(2,3,5,3 Sys::Syslog). Default
              is daemon. Another reasonable choice would be authpriv.

       -d config(1,5) directory
              Defaults to /etc/raddb. Radiusd looks here for its configuration
              files such as the dictionary and the users(1,5) files.

       -i ip-address
              Defines which IP addres to bind(2,n,1 builtins) to  for  sending  and  receiving
              packets- useful for multi-homed hosts.

              This  command  line  option is deprecated.  See the bind_address
              configuration item in(1,8) the radiusd.conf file.

       -b     If the radius server binary was compiled with dbm support,  this
              flag  tells it to actually use the database files instead of the
              flat users(1,5) file.

              This command line option is deprecated, and  does  not  do  any-

       -c     This  is  still  an  experimental  feature.  Cache the password,
              group and shadow(3,5) files in(1,8) a hash-table in(1,8)  memory.   This  makes
              the  radius  process use a bit more memory, but username lookups
              in(1,8) the password file(1,n) are much faster.

              After every change in(1,8) the real password file(1,n) (user added,  pass-
              word  changed) you need to send(2,n) a SIGHUP to the radius server to
              let it re-read its configuration and  the  password/group/shadow(3,5)
              files !

              This  command line option is deprecated.  See the cache configu-
              ration item for the unix module in(1,8) the radiusd.conf file.

       -f     Do not fork, stay running as a foreground process.

       -p port
              Normally radiusd(5,8) listens on the ports specified in(1,8) /etc/services
              (radius  and  radacct).  With this option radiusd(5,8) listens on the
              specified port for authentication requests and on the  specified
              port +1 for accounting requests.

              This command line option is deprecated.  See the port configura-
              tion item in(1,8) the radiusd.conf file.

       -s     Run in(1,8) "single server" mode.  The server normally runs with mul-
              tiple  threads  and/or  processes,  which can lower its response
              time(1,2,n) to requests.  Some systems have issues with threading, how-
              ever,  so  running  in(1,8)  "single server" mode may help to address
              those issues.  In single server mode, the server will  also  not
              "daemonize" (auto-background) itself.

       -v     Print server version(1,3,5) information and exit.

       -x     Debug  mode. In this mode the server will print details of every
              request on it's stderr output. Most useful in(1,8)  combination  with
              -s.  You can specify this option 2 times (-x -x or -xx) to get a
              bit more debugging output.

       -X     Extended debug  mode.   Equivalent  to  -sfxx,  but  simpler  to

       -y     Write   details   about  every  authentication  request  in(1,8)  the
              radius.log file.

              This command line option is deprecated.  See the  log_auth  con-
              figuration item in(1,8) the radiusd.conf file.

       -z     Include  the password in(1,8) the radius.log file(1,n) even for successful
              logins. This is very insecure!.

              This command line option is deprecated.  See  the  log_auth_bad-
              pass  and  the  log_auth_goodpass  configuration  items  in(1,8)  the
              radiusd.conf file.

       Radiusd uses a number of configuration files. Each file(1,n)  has  it's  own
       manpage describing the format of the file. These files are:

              The  main  configuration file(1,n), which sets the administrator-con-
              trolled items.

              This file(1,n) is usually static. It defines all the possible  RADIUS
              attributes  used  in(1,8)  the  other configuration files.  You don't
              have to modify it.  It includes other dictionary  files  in(1,8)  the
              same directory.

              [  Deprecated  ]  Contains  the  IP address and a secret key for
              every client that wants to connect to the server.

              Contains an entry for every NAS (Network Access Server)  in(1,8)  the
              network.  This  is  not  the same as a client, especially if(3,n) you
              have radius proxy server in(1,8) your  network.  In  that  case,  the
              proxy  server  is the client and it sends requests for different

              It also contains a abbreviated name for  each  terminal  server,
              used to create the directory name where the detail file(1,n) is writ-
              ten, and used for the /var/log/radwtmp  file.  Finally  it  also
              defines  what type of NAS (Cisco, Livingston, Portslave) the NAS

       hints  Defines certain hints to the radius server based on the  users(1,5)'s
              loginname or other attributes sent by the access(2,5) server. It also
              provides for mapping user names (such as Pusername -> username).
              This  provides  the functionality that the Livingston 2.0 server
              has as "Prefix" and "Suffix" support in(1,8) the users(1,5) file(1,n),  but  is
              more  general.  Ofcourse  the  Livingston way of doing things is
              also supported, and you can even  use  both  at  the  same  time(1,2,n)
              (within certain limits).

              Defines  the  huntgroups that you have, and makes it possible to
              restrict access(2,5) to certain huntgroups  to  certain  (groups  of)

       users(1,5)  Here the users(1,5) are defined. On a typical setup(2,8), this file(1,n) mainly
              contains DEFAULT entries  to  process  the  different  types  of
              logins,  based  on  hints from the hints file. Authentication is
              then based on the contents of the UNIX /etc/passwd(1,5) file. However
              it is also possible to define all users(1,5), and their passwords, in(1,8)
              this file.

       radiusd.conf(5), users(1,5)(5), huntgroups(5), hints(5), clients(5), dictio-

       The FreeRADIUS Server Project (

                                 23 June 2004                       RADIUSD(8)

References for this manual (incoming links)