FreeRADIUS

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, MariaDB, 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. Please see the documentation directory, which has full documentation for version 4. We do not recommend using AI tools to generate FreeRADIUS configurations. Experience has shown that these configurations are largely wrong. We do recommend using AI tools to analyze your configuration, and suggest optimizations or improvements. However, these suuggestions should be viewed with great suspicion. 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: 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! 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. Read the configuration files. Many parts of the server are documented only with extensive comments in the configuration files. When posting to the mailing list, we recommend posting the output of radiusd -X . That information shows what the server is doing when it receives packets, and how it processes those packets. Do NOT post the configuration files to the mailing list. They're not useful. Instead, post the output of radiusd -X . We really cannot emphasize that enough. 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 have read the documentation relevant to your issue first. 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 posting 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. Technical support, managed systems support, custom deployments, sponsored feature development and many other commercial services are available from InkBridge Networks.