{"id":13439875,"url":"https://github.com/FreeRADIUS/freeradius-server","last_synced_at":"2025-03-20T09:30:59.817Z","repository":{"id":37270879,"uuid":"35649","full_name":"FreeRADIUS/freeradius-server","owner":"FreeRADIUS","description":"FreeRADIUS - A multi-protocol policy server.","archived":false,"fork":false,"pushed_at":"2024-10-29T12:04:24.000Z","size":152543,"stargazers_count":2113,"open_issues_count":85,"forks_count":1077,"subscribers_count":132,"default_branch":"master","last_synced_at":"2024-10-29T13:26:45.232Z","etag":null,"topics":["aaa","arp","authentication","bfd","c","daemon","dhcp","dot1x","eap","freeradius-server","otp","policy","posix","radius","vmps"],"latest_commit_sha":null,"homepage":"http://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/FreeRADIUS.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":".github/contributing.md","funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2008-07-20T18:04:09.000Z","updated_at":"2024-10-29T12:04:28.000Z","dependencies_parsed_at":"2024-01-16T19:46:47.068Z","dependency_job_id":"6533580d-3739-4785-8496-4f1dd406e68c","html_url":"https://github.com/FreeRADIUS/freeradius-server","commit_stats":{"total_commits":44393,"total_committers":260,"mean_commits":170.7423076923077,"dds":0.6096006127092108,"last_synced_commit":"791f6873d67b7a905022802fd4ac9c3abfbd92e2"},"previous_names":[],"tags_count":113,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/FreeRADIUS%2Ffreeradius-server","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/FreeRADIUS%2Ffreeradius-server/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/FreeRADIUS%2Ffreeradius-server/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/FreeRADIUS%2Ffreeradius-server/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/FreeRADIUS","download_url":"https://codeload.github.com/FreeRADIUS/freeradius-server/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":244585690,"owners_count":20476780,"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":["aaa","arp","authentication","bfd","c","daemon","dhcp","dot1x","eap","freeradius-server","otp","policy","posix","radius","vmps"],"created_at":"2024-07-31T03:01:17.825Z","updated_at":"2025-03-20T09:30:59.812Z","avatar_url":"https://github.com/FreeRADIUS.png","language":"C","funding_links":[],"categories":["C","Apps"],"sub_categories":["Security"],"readme":"# The FreeRADIUS server\n\n[![CI build status](https://github.com/FreeRADIUS/freeradius-server/actions/workflows/ci.yml/badge.svg)][BuildStatusLink] [![Coverity status][CoverityStatus]][CoverityStatusLink] [![OSS-Fuzz status][OssFuzz]][OssFuzzLink]\n\n## Introduction\n\nThe FreeRADIUS Server Project is a high performance and highly\nconfigurable multi-protocol policy server, supporting RADIUS, DHCPv4\nDHCPv6, DNS, TACACS+ and VMPS. It is available under the terms of the GNU GPLv2.\nUsing RADIUS allows authentication and authorization for a network\nto be centralized, and minimizes the number of changes that have to\nbe done when adding or deleting new users to a network.\n\nFreeRADIUS 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, Apache Cassandra, Redis, OpenLDAP, and many more.  It is\nused daily to authenticate the Internet access for hundreds of millions\nof people, in sites ranging from 10 to 10 million+ users.\n\n## Documentation\n\nPlease see the [documentation](doc/) directory, which has full\ndocumentation for version 4.\n\nPlease also see \u003chttps://freeradius.org\u003e and \u003chttps://wiki.freeradius.org\u003e\nfor additional documentation.\n\n## Installation\n\nTo install the server, please see the [installation\ninstructions](doc/antora/modules/installation/pages/index.adoc) document.\n\n## Configuring the server\n\nWe 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\nThe 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\n1. Start off with the default configuration files.\n2. Save a copy of the default configuration: It WORKS.  Don't change it!\n3. Verify that the server starts - in debugging mode (`radiusd -X`).\n4. Send it test packets using \"radclient\", or a NAS or AP.\n5. Verify that the server does what you expect\n   - 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   - If it works, proceed to step (6).\n6. Save a copy of the working configuration, along with a note of what\n   you changed, and why.\n7. Make a SMALL change to the configuration.\n8. Repeat from step (3).\n\nThis 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## Debugging the Server\n\nRun 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\nThe debug output is explained in detail in the\n[radiusd-X](https://wiki.freeradius.org/radiusd-X) page on the\n[wiki](https://wiki.freeradius.org).\n\nMany questions are answered on the Wiki:\n\n\u003chttps://wiki.freeradius.org\u003e\n\nRead the configuration files.  Many parts of the server are\ndocumented only with extensive comments in the configuration files.\n\nSearch the mailing lists. For example, using Google, searching\n\"site:lists.freeradius.org \u003csearch term\u003e\" will return results from\nthe FreeRADIUS mailing lists.\n\n\u003chttps://freeradius.org/support/\u003e\n\nInstructions for what to post on the mailing list are [on the\nwiki](https://wiki.freeradius.org/list-help).  Please note that we DO\nrecommend posting the output of `radiusd -X`.  That information shows\nwhat the server is doing when it receives packets, and how it\nprocesses those packets.\n\nWe do NOT recommend posting the configuration files to the mailing\nlist.  They don't help.  Instead, post the output of `radiusd -X`.  We\nreally cannot emphasize that enough.\n\n## Feedback, Defects, and Community Support\n\nIf you have any comments, or are having difficulty getting FreeRADIUS\nto do what you want, please post to the 'freeradius-users' list (see\nthe URL above). The FreeRADIUS mailing list is operated, and\ncontributed to, by the FreeRADIUS community. Users of the list will be\nmore than happy to answer your questions, with the caveat that you\nhave read the documentation relevant to your issue first.\n\nIf you suspect a defect in the server, would like to request a feature,\nor submit a code patch, please use the GitHub issue tracker for the\nfreeradius-server\n[repository](https://github.com/FreeRADIUS/freeradius-server).\nHowever, it is nearly always best to raise the issue on the\nmailing lists first to determine whether it really is a defect or\nmissing feature.\n\nInstructions for gathering data for defect reports can be found in\n[here](doc/antora/modules/developers/pages/bugs.adoc) or on the\n[wiki](https://wiki.freeradius.org/project/bug-reports).\n\nUnder no circumstances should the issue tracker be used for support\nrequests, those questions belong on the user's mailing list.  If you\npost questions related to the server in the issue tracker, the issue\nwill be closed and locked.  If you persist in posting questions to\nthe issue tracker you will be banned from all FreeRADIUS project\nrepositories on GitHub.\n\nPlease 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\nFreeRADIUS is the cumulative effort of many years of work by many\npeople, and you have gotten it for free.  No one is getting paid to\nanswer your questions.  This is free software, and the only way it\ngets better is if you make a contribution back to the project ($$,\ncode, or documentation).\n\n## Commercial support\n\nTechnical support, managed systems support, custom deployments,\nsponsored feature development and many other commercial services\nare available from [Network RADIUS](https://networkradius.com).\n\n[BuildStatus]: https://github.com/FreeRADIUS/freeradius-server/workflows/CI/badge.svg?branch=master \"CI status\"\n[BuildStatusLink]: https://github.com/FreeRADIUS/freeradius-server/actions?query=workflow%3ACI\n[OssFuzz]: https://oss-fuzz-build-logs.storage.googleapis.com/badges/freeradius.svg \"OSS-Fuzz status\"\n[OssFuzzLink]: https://bugs.chromium.org/p/oss-fuzz/issues/list?sort=-opened\u0026can=1\u0026q=proj:freeradius\n[CoverityStatus]: https://scan.coverity.com/projects/58/badge.svg?flat=1 \"Coverity Status\"\n[CoverityStatusLink]: https://scan.coverity.com/projects/58\n[LGTMStatus]: https://img.shields.io/lgtm/alerts/g/FreeRADIUS/freeradius-server.svg?logo=lgtm\u0026logoWidth=18\n[LGTMStatusLink]: https://lgtm.com/projects/g/FreeRADIUS/freeradius-server/alerts/\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FFreeRADIUS%2Ffreeradius-server","html_url":"https://awesome.ecosyste.ms/projects/github.com%2FFreeRADIUS%2Ffreeradius-server","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FFreeRADIUS%2Ffreeradius-server/lists"}