Skip to content
FreeRADIUS - A multi-protocol policy server.
Branch: master
Clone or download
Latest commit fda6efe Jun 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github move bugs.md to doc/source/ directory Jun 2, 2019
debian fix debian/ubuntu package build May 10, 2019
doc typo Jun 19, 2019
m4 Remove CC_BOUNDED and use static array subscript for bounds enforcement Jan 6, 2019
man add MEMBER keyword to dictionaries for 'struct' May 14, 2019
mibs Add triggers for min/max reserve time for connection pools Feb 10, 2016
raddb formatting Jun 19, 2019
redhat add mod-config/csv May 24, 2019
scripts eapol_test: Build the stable 2.8 version Jun 19, 2019
share Update dictionary.rfc8045 Jun 14, 2019
src more "get rid of struct timeval". Jun 19, 2019
suse su to radiusd user/group when rotating logs May 7, 2019
.clang-format Example .clang-format config which gets us somewhere close to the for… May 31, 2018
.gitattributes FreeRADIUS is C11. Non of that Apple junk... Sep 13, 2016
.gitignore Add capability to 'make rpm' check the dependencies Apr 3, 2019
.travis.yml Revert "Work around a bug where Travis truncates logs and fails" May 15, 2019
CODE_OF_CONDUCT.md Add note on biases Sep 19, 2018
COPYRIGHT more cleanups Jun 16, 2019
CREDITS Misc Non-code impacting changes to docs Oct 9, 2017
INSTALL.md Misc Non-code impacting changes to docs Oct 9, 2017
LICENSE Update LICENSE Jul 1, 2018
Make.inc.in add pandoc / asciidoc to configure checks. Fixes #2622 Apr 23, 2019
Makefile start running integration tests on jenkins May 15, 2019
README.md move bugs.md to doc/source/ directory Jun 2, 2019
VERSION Bump VERSION Aug 6, 2016
acinclude.m4 check for brew version of readline Jul 12, 2018
aclocal.m4 Let aclocal update aclocal.m4, fixes #1517 Feb 15, 2016
autogen.sh Rename configure.in to configure.ac Jun 23, 2013
config.guess Pulled from GNU. This closes bug #496 Dec 15, 2007
config.sub Pulled from GNU. This closes bug #496 Dec 15, 2007
configure Remove function checks Jun 10, 2019
configure.ac Remove function checks Jun 10, 2019
install-sh Update install-sh to version 2016-01-11.22 Sep 17, 2016
main.mk Moved raddb/ to use boilermake Feb 26, 2013
missing Rename configure.in to configure.ac Jun 23, 2013

README.md

The FreeRADIUS server

Travis CI build status Coverity Status

Introduction

The FreeRADIUS Server Project is a high performance and highly configurable multi-protocol policy server, supporting RADIUS, DHCPv4 and VMPS. It is available under the terms of the GNU GPLv2. Using RADIUS allows authentication and authorization for a network to be centralized, and minimizes the number of changes that have to be done when adding or deleting new users to a network.

FreeRADIUS can authenticate users on systems such as 802.1x (WiFi), dialup, PPPoE, VPN's, VoIP, and many others. It supports back-end databases such as MySQL, PostgreSQL, Oracle, Microsoft Active Directory, Apache Cassandra, Redis, OpenLDAP, and many more. It is used daily to authenticate the Internet access for hundreds of millions of people, in sites ranging from 10 to 10 million+ users.

Upgrading

Version 4.0.x of the server is largely compatible with version 3.0.x, but be sure to address any warnings when starting v3.0.x before attempting to use en existing configuration with v4.0.x.

For a list of changes in version 4.0, please see doc/ChangeLog

See raddb/README.md for information on what to do to update your configuration.

Administrators upgrading from a previous version should install this version in a different location from their existing systems. Any existing configuration should be carefully migrated to the new version, in order to take advantage of the new features which can greatly simply configuration.

Please see https://freeradius.org and https://wiki.freeradius.org for more information.

Installation

To install the server, please see the INSTALL.md file in this directory.

Configuring the server

We understand that the server may be difficult to configure, install, or administer. It is, after all, a complex system with many different configuration possibilities.

The most common problem is that people change large amounts of the configuration without understanding what they're doing, and without testing their changes. The preferred method of operation is the following:

  1. Start off with the default configuration files.
  2. Save a copy of the default configuration: It WORKS. Don't change it!
  3. Verify that the server starts - in debugging mode (radiusd -X).
  4. Send it test packets using "radclient", or a NAS or AP.
  5. Verify that the server does what you expect
    • If it does not work, change the configuration, and go to step (3)
    • If you're stuck, revert to using the "last working" configuration.
    • If it works, proceed to step (6).
  6. Save a copy of the working configuration, along with a note of what you changed, and why.
  7. Make a SMALL change to the configuration.
  8. Repeat from step (3).

This method will ensure that you have a working configuration that is customized to your site as quickly as possible. While it may seem frustrating to proceed via a series of small steps, the alternative will always take more time. The "fast and loose" way will be MORE frustrating than quickly making forward progress!

Debugging the Server

Run the server in debugging mode, (radiusd -X) and READ the output. We cannot emphasize this point strongly enough. The vast majority of problems can be solved by carefully reading the debugging output, which includes WARNINGs about common issues, and suggestions for how they may be fixed.

Many questions are answered on the Wiki:

https://wiki.freeradius.org

Read the configuration files. Many parts of the server are documented only with extensive comments in the configuration files.

Search the mailing lists. For example, using Google, searching "site:lists.freeradius.org " will return results from the FreeRADIUS mailing lists.

https://freeradius.org/support/

Feedback, Defects, and Community Support

If you have any comments, or are having difficulty getting FreeRADIUS to do what you want, please post to the 'freeradius-users' list (see the URL above). The FreeRADIUS mailing list is operated, and contributed to, by the FreeRADIUS community. Users of the list will be more than happy to answer your questions, with the caveat that you've read documentation relevant to your issue first.

If you suspect a defect in the server, would like to request a feature, or submit a code patch, please use the GitHub issue tracker for the freeradius-server repository. However, it is nearly always best to raise the issue on the mailing lists first to determine whether it really is a defect or missing feature.

Instructions for gathering data for defect reports can be found in doc/source/bugs.md or on the wiki.

Under no circumstances should the issue tracker be used for support requests, those questions belong on the user's mailing list. If you post questions related to the server in the issue tracker, the issue will be closed and locked. If you persist in positing questions to the issue tracker you will be banned from all FreeRADIUS project repositories on GitHub.

Please do NOT complain that the developers aren't answering your questions quickly enough, or aren't fixing the problems quickly enough. Please do NOT complain if you're told to go read documentation. We recognize that the documentation isn't perfect, but it does exist, and reading it can solve most common questions.

FreeRADIUS is the cumulative effort of many years of work by many people, and you've gotten it for free. No one is getting paid to answer your questions. This is free software, and the only way it gets better is if you make a contribution back to the project ($$, code, or documentation).

We will note that the people who get most upset about any answers to their questions usually do not have any intention of contributing to the project. We will repeat the comments above: no one is getting paid to answer your questions or to fix your bugs. If you don't like the responses you are getting, then fix the bug yourself, or pay someone to address your concerns. Either way, make sure that any fix is contributed back to the project so that no one else runs into the same issue.

Books on RADIUS

See doc/README.md for more information about FreeRADIUS.

There is an O'Reilly book available. It serves as a good introduction for anyone new to RADIUS. However, it is from 2002 and is not much more than a basic introduction to the subject.

https://www.amazon.com/exec/obidos/ASIN/0596003226/freeradiusorg-20/

Commercial support

Technical support, managed systems support, custom deployments, sponsored feature development and many other commercial services are available from Network RADIUS.

You can’t perform that action at this time.