{"id":16850407,"url":"https://github.com/jacques/freeradius","last_synced_at":"2025-04-10T20:32:29.926Z","repository":{"id":66394036,"uuid":"35596","full_name":"jacques/freeradius","owner":"jacques","description":"FreeRADIUS public git repository (clone of git.freeradius.org)","archived":false,"fork":false,"pushed_at":"2010-05-29T10:00:20.000Z","size":14512,"stargazers_count":5,"open_issues_count":0,"forks_count":1,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-03-24T18:06:08.347Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"http://www.freeradius.org/","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/jacques.png","metadata":{"files":{"readme":"README","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2008-07-20T10:18:21.000Z","updated_at":"2023-01-10T03:56:03.000Z","dependencies_parsed_at":"2023-02-20T03:30:54.757Z","dependency_job_id":null,"html_url":"https://github.com/jacques/freeradius","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jacques%2Ffreeradius","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jacques%2Ffreeradius/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jacques%2Ffreeradius/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jacques%2Ffreeradius/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/jacques","download_url":"https://codeload.github.com/jacques/freeradius/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248290033,"owners_count":21078923,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-13T13:22:37.491Z","updated_at":"2025-04-10T20:32:29.871Z","avatar_url":"https://github.com/jacques.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"1. INTRODUCTION\n\n  The FreeRADIUS Server Project is a high performance and highly\nconfigurable RADIUS server that is available under the terms of the\nGNU GPLv2.  Using RADIUS allows authentication and authorization for a\nnetwork to be centralized, and minimizes the number of changes that\nhave to be done when adding or deleting new users to a network.\n\n  FreeRADIUS can authenticate users on systems such as 802.1x (WiFi),\ndialup, PPPoE, VPN's, VoIP, and many others.  It supports back-end\ndatabases such as MySQL, PostgreSQL, Oracle, Microsoft Active\nDirectory, OpenLDAP, and many more.  It is used daily to authenticate\nthe Internet access for hundreds of millions of people, in sites\nranging from 10 users, to 10 million and more users.\n\n  Version 2.0 of the server is intended to be backwards compatible\nwith previous versions, but also to have many new features, such as:\n\n  * simple policy language (see \"man unlang\")\n  * virtual servers (raddb/sites-available/README)\n  * IPv6 support\n  * better proxy support (raddb/proxy.conf)\n  * More EAP types\n  * Debugging output should be MUCH easier to understand\n  * VMPS support\n  * More modules are marked \"stable\" (python, etc.)\n  * SQL configuration has been cleaned up (see raddb/sql/*)\n  * limited support for HUP\n  * check configuration and exit (radiusd -C)\n  * Server core is now event based (simpler, more powerful)\n\n  Administrators upgrading from a previous version should install this\nversion in a different location from their existing systems.  Any\nexisting configuration should be carefully migrated to the new\nversion, in order to take advantage of the new features which can\ngreatly simply configuration.\n\n  While every attempt has been made to ensure that this version is\nbackwards compatible with previous versions, there may be cases where\nit is not backwards compatible.  In most cases, incompatibilities are\na side-effect of fixing bugs, or of adding new features.  Some\nconfiguration differences are noted below:\n\n  * The recommended format for clients has changed.  See \"clients.conf\".\n    The old format should still work, but should be changed to use the\n    new format.\n\n  * The recommended formant for realms has changed.  See \"proxy.conf\"\n    The old format should still work, but should be changed to use the\n    new format.  In addition, the new format has much more flexibility.\n\n  * Any configuration using TTLS or PEAP should be updated to use\n    virtual servers. See \"virtual_server\" in \"eap.conf\", and\n    \"raddb/sites-available/inner-tunnel\".  In most cases, using an\n    \"inner-tunnel\" virtual server will make the configuration MUCH\n    simpler.\n\n  * A number of deprecated command-line options have been removed.\n    (-y -z -A -l -g) See \"man radiusd\".  These configurations can be\n    controlled in \"radiusd.conf\", so it is not necessary to have them\n    as command-line options.\n\n  Please see http://freeradius.org and http://wiki.freeradius.org for\nmore information.\n\n\n2. INSTALLATION\n\n  To install the server, please see the INSTALL file in this\ndirectory.\n\n\n3. DEBUGGING THE SERVER\n\n  Run the server in debugging mode, (radiusd -X) and READ the output.\nWe cannot emphasize this point strongly enough.  The vast majority of\nproblems can be solved by carefully reading the debugging output,\nwhich includes WARNINGs about common issues, and suggestions for how\nthey may be fixed.\n\n  Read the FAQ.  Many questions are answered there.  See the Wiki\n\n\thttp://wiki.freeradius.org\n\n  Read the configuration files.  Many parts of the server have NO\ndocumentation, other than comments in the configuration file.\n\n  Search the mailing lists.  There is a Google link on the bottom of\n  the page:\n\n\thttp://www.freeradius.org/list/users.html\n\n  Type some key words into the search box, and you should find\ndiscussions about common problems and solution.\n\n\n4. ADDITIONAL INFORMATION\n\n  See 'doc/README' for more information about FreeRADIUS.\n\n  There is an O'Reilly book available.  It serves as a good\nintroduction for anyone new to RADIUS.  However, it is almost 5 years\nold, and is not much more than a basic introduction to the subject.\n\nhttp://www.amazon.com/exec/obidos/ASIN/0596003226/freeradiusorg-20/\n\n  For other RADIUS information, the Livington internet site had a lot\nof information about radius online.  Unfortunately Livingston, and the\nsite, don't exist anymore but there is a copy of the site still at:\n\n\thttp://portmasters.com/www.livingston.com/\n\n  Especially worth reading is the \"RADIUS for Unix administrators guide\"\n\nHTML:  http://portmasters.com/tech/docs/radius/1185title.html\nPDF:   http://portmasters.com/tech/docs/pdf/radius.pdf\n\n\n5. PROBLEMS AND CONCERNS\n\n  We understand that the server may be difficult to configure,\ninstall, or administer.  It is, after all, a complex system with many\ndifferent configuration possibilities.\n\n  The most common problem is that people change large amounts of the\nconfiguration without understanding what they're doing, and without\ntesting their changes.  The preferred method of operation is the\nfollowing:\n\n   1) Start off with the default configuration files.\n   2) Save a copy of the default configuration: It WORKS.  Don't change it!\n   3) Verify that the server starts.  (You ARE using debugging mode, right?)\n   4) Send it test packets using \"radclient\", or a NAS or AP.\n   5) Verify that the server does what you expect.\n     a) If it does not work, change the configuration, and go to step (3)\n        If you're stuck, revert to using the \"last working\" configuration.\n     b) If it works, proceed to step (6).\n   6) Save a copy of the working configuration, along with a note\n      of what you changed, and why.\n   7) Make a SMALL change to the configuration.\n   8) Repeat from step (3).\n\n  This method will ensure that you have a working configuration that\nis customized to your site as quickly as possible.  While it may seem\nfrustrating to proceed via a series of small steps, the alternative\nwill always take more time.  The \"fast and loose\" way will be MORE\nfrustrating than quickly making forward progress!\n\n\n6. FEEDBACK\n\n  If you have any comments, bug reports, problems, or concerns, please\nsend them to the 'freeradius-users' list (see the URL above).  We will\ndo our best to answer your questions, to fix the problems, and to\ngenerally improve the server in any way we can.\n\n  Please do NOT complain that the developers aren't answering your\nquestions quickly enough, or aren't fixing the problems quickly\nenough.  Please do NOT complain if you're told to go read\ndocumentation.  We recognize that the documentation isn't perfect, but\nit *does* exist, and reading it can solve most common questions.\n\n  FreeRADIUS is the cumulative effort of many years of work by many\npeople, and you've gotten it for free.  No one gets paid to work on\nFreeRADIUS, and no one is getting paid to answer your questions.  This\nis free software, and the only way it gets better is if you make a\ncontribution back to the project ($$, code, or documentation).\n\n  We will note that the people who get most upset about any answers to\ntheir questions usually do not have any intention of contributing to\nthe project.  We will repeat the comments above: no one is getting\npaid to answer your questions or to fix your bugs.  If you don't like\nthe responses you are getting, then fix the bug yourself, or pay\nsomeone to address your concerns.  Either way, make sure that any fix\nis contributed back to the project so that no one else runs into the\nsame issue.\n\n  Support IS available: http://freeradius.org/business\n\n  Please submit bug reports, suggestions, or patches.  That feedback\ngives the developers a guide as to where they should focus their work.\nIf you like the server, feel free to mail the list and say so.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjacques%2Ffreeradius","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjacques%2Ffreeradius","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjacques%2Ffreeradius/lists"}