in a way that will better fit with the long-term vision for the server.
Once you've got the go ahead, please read through the
-[coding standards document](https://wiki.freeradius.org/contributing/coding-standards).
+[coding standards](https://www.freeradius.org/documentation/freeradius-server/4.0.0/developers/coding-methods.html) document.
If you're creating a new module you may wish to read the
-[module creation guide](https://wiki.freeradius.org/contributing/Modules3).
+[module creation guide](https://www.freeradius.org/documentation/freeradius-server/4.0.0/developers/module_interface.html).
You may also wish to utilise the [doxygen site](https://doc.freeradius.org) to review code documentation.
Finally, this file was written to be displayed automatically on the GitHub issue tracker, so
Git/GitHub knowledge is assumed. If you're wondering what a pull-request is, this document may be of
-some use <https://wiki.freeradius.org/contributing/GitHub>.
+some use <https://www.freeradius.org/documentation/freeradius-server/4.0.0/developers/github.html>
## Continuous Integration Tests (CIT)
Please see the [documentation](doc/) directory, which has full
documentation for version 4.
-Please also see <https://freeradius.org> and <https://wiki.freeradius.org>
+Please also see <https://freeradius.org> and <https://www.freeradius.org/documentation/freeradius-server/4.0.0/>
for additional documentation.
## Installation
they may be fixed.
The debug output is explained in detail in the
-[radiusd-X](https://wiki.freeradius.org/radiusd-X) page on the
-[wiki](https://wiki.freeradius.org).
-
-Many questions are answered on the Wiki:
-
-<https://wiki.freeradius.org>
+[radiusd-X](https://www.freeradius.org/documentation/freeradius-server/4.0.0/debugging/radiusd_X.html)
+page.
Read the configuration files. Many parts of the server are
documented only with extensive comments in the configuration files.
"site:lists.freeradius.org <search term>" will return results from
the FreeRADIUS mailing lists.
-<https://freeradius.org/support/>
+[Additional
+help](https://www.freeradius.org/documentation/freeradius-server/4.0.0/gethelp.html)
+is available via the mailing lists, including commercial support.
+
+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.
-Instructions for what to post on the mailing list are [on the
-wiki](https://wiki.freeradius.org/list-help). Please note that we DO
-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.
-We do NOT recommend posting the configuration files to the mailing
-list. They don't help. Instead, post the output of `radiusd -X`. We
-really cannot emphasize that enough.
+DO post a clear description ofwhat the problem is. Empty questions
+will not make you friends. e.g. "I changed things and now it doesn't
+work. What do I do to fix it?"
## Feedback, Defects, and Community Support
missing feature.
Instructions for gathering data for defect reports can be found in
-[here](doc/antora/modules/developers/pages/bugs.adoc) or on the
-[wiki](https://wiki.freeradius.org/project/bug-reports).
+[here](doc/antora/modules/developers/pages/bugs.adoc) and online at
+<https://www.freeradius.org/documentation/freeradius-server/4.0.0/developers/bugs.html>
Under no circumstances should the issue tracker be used for support
requests, those questions belong on the user's mailing list. If you
[Unit]
Description=FreeRADIUS multi-protocol policy server
After=network-online.target
-Documentation=man:radiusd(8) man:radiusd.conf(5) https://wiki.freeradius.org/ https://freeradius.org/documentation/freeradius-server/
+Documentation=man:radiusd(8) man:radiusd.conf(5) https://freeradius.org/documentation/freeradius-server/
[Service]
Type=notify
https://lists.freeradius.org/mailman/listinfo/freeradius-users[User's
mailing list].
-Some of the documents here started life as pages on
-https://wiki.freeradius.org[wiki.freeradius.org]. If you've just been
-through a particularly arduous service configuration and deployment, and would
-like to help your fellow users, then please create a new how to on the wiki.
-If it's popular enough, we'll include it in the official documentation for the
-next release.
+Some of the documents here started life as pages on the old
+Wiki. However, there were eventually very few contributions to it.
+The full documentation is now maintained by [InkBridge
+Networks](https://inkbridgenetworks.com) (previously Network
+RADIUS).
// Copyright (C) 2025 Network RADIUS SAS. Licenced under CC-by-NC 4.0.
// This documentation was developed by Network RADIUS SAS.
debug output. If the issues are still clear, then ask a question on
the
https://lists.freeradius.org/mailman/listinfo/freeradius-users[freeradius-users]
-mailing list. Please also read the
-https://wiki.freeradius.org/list-help[list help] instructions, for
-what information we need in order to help you. This information is
-typically an explanation of what you are trying to achieve, what
-exactly isn't working and provide the full debugging output for a
-relevant test run.
+mailing list. Please also see <https://www.freeradius.org/documentation/freeradius-server/4.0.0/gethelp.html>
====
====
If you do no receive an IP address then start FreeRADIUS in debugging mode
to determine where the process if failing as described in the
-https://wiki.freeradius.org/guide/radiusd-X[guide to debugging FreeRADIUS]. Do
+https://www.freeradius.org/documentation/freeradius-server/4.0.0/debugging/radiusd_X.html[guide to debugging FreeRADIUS]. Do
not proceed until you have resolved the IP allocation issue.
====
output from FreeRADIUS, which will usually tell you what is wrong.
See [how to read the debug
-output](http://wiki.freeradius.org/radiusd-X) for instructions on
-reading amd understanding the debug output.
+output](https://www.freeradius.org/documentation/freeradius-server/4.0.0/debugging/radiusd_X.html) for instructions on
+reading and understanding the debug output.
The next step is to xref:protocols/radius/radsec_client.adoc[configure
FreeRADIUS as a RadSec test client] so that we can verify that our
=== rlm_rest
`REST-HTTP-Code` is now inserted into the `request` list instead
-of the `reply.` list, to be compliant with the
-https://wiki.freeradius.org/guide/List-Usage[list usage] guidelines.
+of the `reply.` list.
[#rlm_sql]
=== rlm_sql
}
----
-For more detailed examples, see the Wiki page:
-https://wiki.freeradius.org/upgrading/version4/proxy. That page also
-describes how to upgrade a v3 configuration to the new v4 style.
-
The benefit of this approach is that the "RADIUS proxy" functionality
is just another module. It is now possible to not just fail over from
one home server to another, but also to proxy the same packet to
section titled DEBUGGING. It outlines a method where you can
quickly obtain the configuration you want, without running into
trouble. And finally, the debug output can be complex. Please read
-https://wiki.freeradius.org/radiusd-X[debugging] to understand that output.
+https://www.freeradius.org/documentation/freeradius-server/4.0.0/debugging/radiusd_X.html
The best way to configure the server for your local system is to
*carefully* edit this file. Most attempts to make large edits to
```
Look in an SQL database. The schema of the database is
-meant to mirror the `users` file. For a full description
-of the module behavior, please see
-https://wiki.freeradius.org/modules/Rlm_sql
+meant to mirror the `users` file.
```
-sql
The `ldap` module reads passwords and other attributes from
an LDAP database.
-For a full description of the module behavior, please see
-https://wiki.freeradius.org/modules/Rlm_ldap
-
```
-ldap
Since version 4, proxying also happens in this section. For more
information on how proxying has changed in version 4, please see
-https://wiki.freeradius.org/upgrading/version4/proxy.
+https://www.freeradius.org/documentation/freeradius-server/4.0.0/howto/upgrade/proxy.html
For authentication, you should generally NOT set the `Auth-Type`
attribute. As noted above, the modules will usually figure it what
* note that this won't work for EAP.
For more information, see:
-https://wiki.freeradius.org/upgrading/version4/proxy.
+https://www.freeradius.org/documentation/freeradius-server/4.0.0/howto/upgrade/proxy.html
# section titled DEBUGGING. It outlines a method where you can
# quickly obtain the configuration you want, without running into
# trouble. And finally, the debug output can be complex. Please read
-# https://wiki.freeradius.org/radiusd-X[debugging] to understand that output.
+# https://www.freeradius.org/documentation/freeradius-server/4.0.0/debugging/radiusd_X.html
#
# The best way to configure the server for your local system is to
# *carefully* edit this file. Most attempts to make large edits to
#
# Look in an SQL database. The schema of the database is
- # meant to mirror the `users` file. For a full description
- # of the module behavior, please see
- # https://wiki.freeradius.org/modules/Rlm_sql
+ # meant to mirror the `users` file.
#
-sql
# The `ldap` module reads passwords and other attributes from
# an LDAP database.
#
- # For a full description of the module behavior, please see
- # https://wiki.freeradius.org/modules/Rlm_ldap
- #
-ldap
#
#
# Since version 4, proxying also happens in this section. For more
# information on how proxying has changed in version 4, please see
-# https://wiki.freeradius.org/upgrading/version4/proxy.
+# https://www.freeradius.org/documentation/freeradius-server/4.0.0/howto/upgrade/proxy.html
#
# For authentication, you should generally NOT set the `Auth-Type`
# attribute. As noted above, the modules will usually figure it what
# * note that this won't work for EAP.
#
# For more information, see:
-# https://wiki.freeradius.org/upgrading/version4/proxy.
+# https://www.freeradius.org/documentation/freeradius-server/4.0.0/howto/upgrade/proxy.html
#
#
- The files in this directory are intended only for "generic" systems.
+The files in this directory are intended only for "generic" systems.
If you need to build FreeRADIUS from source on a RedHat system (RHEL,
-Fedora, or CentOS), please read the following FAQ:
+etc.), please see the following document:
- http://wiki.freeradius.org/guide/Red-Hat-FAQ
-
- It was written by the person who maintains the RedHat FreeRADIUS
-packages, and contains detailed instructions for creating an RPM from
-the original RedHat spec files. This ensures that the RPMs on your
-system closely match the RedHat requirements.
+https://www.freeradius.org/documentation/freeradius-server/4.0.0/howto/installation/redhat.html
# add Red Hat specific documentation
%__cat >> $RPM_BUILD_ROOT/%{docdir}/REDHAT << EOF
-Red Hat, RHEL, Fedora, and CentOS specific information can be found on the
-FreeRADIUS Wiki in the Red Hat FAQ.
-
-http://wiki.freeradius.org/guide/Red_Hat_FAQ
-
-Please reference that document.
+Red Hat, RHEL, Fedora, and CentOS specific information can be found
+online in the FreeRADIUS documentation:
+https://www.freeradius.org/documentation/freeradius-server/4.0.0/howto/installation/redhat.html
EOF
# Install the selinux module
[Unit]
Description=FreeRADIUS multi-protocol policy server
After=network-online.target
-Documentation=man:radiusd(8) man:radiusd.conf(5) https://wiki.freeradius.org/ https://freeradius.org/documentation/freeradius-server/
+Documentation=man:radiusd(8) man:radiusd.conf(5) https://freeradius.org/documentation/freeradius-server/
[Service]
Type=notify
ATTRIBUTE VC-groups 192 string
-# See http://wiki.freeradius.org/vendor/HP#Capability-advertisements
+# See https://www.freeradius.org/documentation/freeradius-server/4.0.0/howto/vendors/hp.html
ATTRIBUTE Capability-Advert 255 octets
# Management-Protocol
ROPTIONAL(RWDEBUG, WARN, "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!");
ROPTIONAL(RWDEBUG, WARN, "!! EAP session %016" PRIxPTR " did not finish! !!",
(uintptr_t)eap_session);
- ROPTIONAL(RWDEBUG, WARN, "!! See http://wiki.freeradius.org/guide/Certificate_Compatibility !!");
+ ROPTIONAL(RWDEBUG, WARN, "!! See https://www.freeradius.org/documentation/freeradius-server/4.0.0/trouble-shooting/client.html !!");
ROPTIONAL(RWDEBUG, WARN, "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!");
}