Setting Up a FreeRADIUS Server

WHAT?
FreeRADIUS is the open source RADIUS server implementation for
AAA (Authentication, Authorization, and Accounting).

WHY?
This article provides a complete overview of the FreeRADIUS server
setup and basic FreeRADIUS configuration for testing.

EFFORT
It takes 15 minutes to install and configure FreeRADIUS. You need up
to an hour to fully understand the FreeRADIUS architecture and func-
tionality.

GOAL
Basic understanding of setting up and testing a FreeRADIUS server.

REQUIREMENTS

A virtual machine or instance to install FreeRADIUS.

Another virtual machine on your network to test client functions.

Publication Date: 11 Jan 2024

Contents
1 The FreeRADIUS concept 3

1 Setting Up a FreeRADIUS Server

 2 Installing the FreeRADIUS server 3

3 Creating test certificates on the server 4

4 Starting FreeRADIUS on the server 4

5 Adding a test client with a user on the server 5

6 Starting the FreeRADIUS daemon on the server 7

7 Testing authentication on the client 7

8 Troubleshooting FreeRADIUS 8

9 Legal Notice 9

A GNU Free Documentation License 10

2 Setting Up a FreeRADIUS Server

1 The FreeRADIUS concept
The RADIUS (Remote Authentication Dial-In User Service) protocol is a standard
service for managing network access. FreeRADIUS is the open source RADIUS server
implementation and the most widely used RADIUS server.
FreeRADIUS verifies users and clients and manages network access and operations. FreeRADIUS
ensures secure communication between network devices and user authentication servers.
FreeRADIUS performs authentication, authorization and accounting (AAA) for very large busi-
nesses such as Internet service providers and cellular network providers, and is also popular for
small networks. It authenticates users and devices, authorizes those users and devices for certain
network services, and tracks the use of services for billing and auditing. You do not have to use
all three of the AAA protocols, use only the ones you need.
RADIUS operates over a distributed architecture and runs separately from the Network Access
Server (NAS). User access data is stored on a central RADIUS server that is available to multiple
NAS devices. The NAS provides physical access to the network, such as a managed Ethernet
switch or a wireless access point. FreeRADIUS verifies and manages network access and oper-
ations. FreeRADIUS ensures secure communication between network devices and user authen-
tication servers. To set up a FreeRADIUS server, you must install, configure and define user
accounts, and define and determine authentication and authorization for FreeRADIUS. After
installing FreeRADIUS, you must test the function by integrating FreeRADIUS with the devices
to be managed.

FIGURE 1: FREERADIUS ARCHITECTURE

This article includes an example that shows installing FreeRADIUS, creating a set of test cer-
tificates, starting the server, adding client server and user, testing authentication, and testing
multiple clients.

2 Installing the FreeRADIUS server

The following example shows how to install a FreeRADIUS server. Ensure that you
install the freeradius-server and freeradius-server-utils packages on a
separate machine from your Network Access Server (NAS).

3 Setting Up a FreeRADIUS Server

Install freeradius-server and freeradius-server-utils .

> sudo sudo zypper install freeradius-server and freeradius-server-utils

3 Creating test certificates on the server

Certificates enable secure communication between the FreeRADIUS clients and the
FreeRADIUS server.
To allow access to the server, certificate authentication is required. To test the au-
thentication using FreeRADIUS, you can create test certificates. The following ex-
ample shows how to create test certificates to test FreeRADIUS. Ensure that you re-
move the test certificates and use the correct certificates after testing FreeRADIUS.

Note

The test certificates created are not suitable for production use.

Create a set of test certificates in /etc/raddb/certs .

> cd /etc/raddb/certs
./bootstrap

When you are satisfied with your testing and ready to create a production configuration, remove
all the test certificates in /etc/raddb/certs and replace them with your own certificates.

4 Starting FreeRADIUS on the server

You must start FreeRADIUS on the server after installation.

PROCEDURE 1: STARTING FREERADIUS

After the bootstrap is complete, start the server in debugging mode as a root user.

4 Setting Up a FreeRADIUS Server

 To do this, run the following command:

Note
Start the FreeRADIUS server in debugging mode only for testing. Other than for
testing, use sudo systemctl start freeradius

> sudo radiusd -X

[...]
Listening on auth address * port 1812 bound to server default
Listening on acct address * port 1813 bound to server default
Listening on auth address :: port 1812 bound to server default
Listening on acct address :: port 1813 bound to server default
Listening on auth address 127.0.0.1 port 18120 bound to server inner-tunnel
Listening on proxy address * port 54435
Listening on proxy address :: port 58415
Ready to process requests

The Listening and Ready to process requests appear when the server starts cor-
rectly.

5 Adding a test client with a user on the server

You can add a client and a user to test authentication for the FreeRADIUS server.
The client is a client of the RADIUS server, such as a wireless access point or switch.
The users are added in the user configuration le and the clients are added in the
client configuration le. These configuration les are stored on the server where
FreeRADIUS is installed.
The machines that can use the devices of the FreeRADIUS server are defined in the
client.conf le.

PROCEDURE 2: CONFIGURING USERS AND CLIENTS

Add the machines that can use the devices of the FreeRADIUS server and the users by
using the following example:

1. Configure users in the authorization le, /etc/raddb/mods-config/files/authorize .

5 Setting Up a FreeRADIUS Server

 To do this, open /etc/raddb/mods-config/files/authorize and uncomment the fol-
lowing lines:

bob Cleartext-Password := "hello"

Reply-Message := "Hello, %{User-Name}"

"john" Cleartext-Password := "newpassword"

Service-Type = New-User,
Framed-IP-Address = 190.155.2.50

2. Add a test client and user to test the authentication in /etc/raddb/client.conf .

vi /etc/raddb/client.conf

A test client, localhost, is provided in /etc/raddb/client.conf , with the secret test-

ing123 .

client private-networks {
ipaddr = 190.1.0/22
secret = testingabc-1
}
client common-network {
ipaddr = 191.1.0/27
secret = testingxyz
}

3. Add clients of the RADIUS server, such as a wireless access point, network switch, or
another form of NAS.
Create a client configuration on your server by using the following example.
Uncomment the following entry in /etc/raddb/client.conf and use the IP address of
your test client machine or access gateway instead of the given IP address.

client private-network-1 {
ipaddr = 192.0.2.0/24
secret = testing123-1
}

You must also configure the client to talk to the RADIUS server by using the IP address of
the machine running the RADIUS server. The client must use the same secret as configured
above in the client section.

4. On the client machine, install freeradius-server-utils .

> sudo sudo zypper install freeradius-server and freeradius-server-utils

6 Setting Up a FreeRADIUS Server

You can now add more users and configure databases.
Run one more login test from a different computer on your network.

6 Starting the FreeRADIUS daemon on the server

After adding client and user, you must start the FreeRADIUS daemon.

PROCEDURE 3: STARTING THE FREERADIUS DAEMON

Start the FreeRADIUS daemon to provide authentication, authorization, and accounting

(AAA) services in a network environment for network access control and network access
management.

1. Start the FreeRADIUS daemon.

> sudo systemctl restart freeradius

2. Enable auto-start for FreeRADIUS on system boot up.

> sudo systemctl enable freeradius

7 Testing authentication on the client

You can test the authentication for the newly added user in FreeRADIUS.

PROCEDURE 4: TESTING AUTHENTICATION

Test the authentication for the newly added user using the following example:

Open a new terminal, and as an unprivileged user, use the radtest command to log in
as the newly added user bob .

> radtest bob hello 127.0.0.1 0 testing123

Sent Access-Request Id 241 from 0.0.0.0:35234 to 127.0.0.1:1812 length 73
User-Name = "bob"
User-Password = "hello"
NAS-IP-Address = 127.0.0.1
NAS-Port = 0
Message-Authenticator = 0x00

7 Setting Up a FreeRADIUS Server

 Cleartext-Password = "hello"
Received Access-Accept Id 241 from 127.0.0.1:1812 to 0.0.0.0:0 length 20

After the authentication is successful, a login message appears in the terminal in which
you started FreeRADIUS, as shown below.

(3) pap: Login attempt with password

(3) pap: Comparing with "known good" Cleartext-Password
(3) pap: User authenticated successfully
(3) [pap] = ok
[...]
(3) Sent Access-Accept Id 241 from 127.0.0.1:1812 to 127.0.0.1:35234
length 0
(3) Finished request
Waking up in 4.9 seconds.
(3) Cleaning up request packet ID 241 with timestamp +889

The access request is successful and the authentication methods PAP, CHAP, MS-CHAPv1,
MS-CHAPv2, PEAP, EAP-TTLS, EAP-GTC, EAP-MD5 work for the user bob .

8 Troubleshooting FreeRADIUS

There are several test users and test clients provided. Ensure that your server has
the correct firewall settings. If your test logins fail, review all the output to under-
stand the issues.
Possible troubleshooting methods are given below:

Check FreeRADIUS logs in /var/log/freeradius/radius.log or /var/log/ra-

dius/radius.log .

Check if FreeRADIUS is running.

systemctl status freeradius

If FreeRADIUS is not running, start FreeRADIUS.

systemctl start freeradius

If a FreeRADIUS server is already running, an error Address already in use appears.

Stop that server before running the server in debugging mode.

8 Setting Up a FreeRADIUS Server

 If the server does not start, verify the output. The output includes the details about the
errors. You can direct the output to a text le with tee:

radiusd -X | tee radiusd.text

Check if the ports for FreeRADIUS in the firewall are open for communication.

Check user authentication.

radtest username password localhost 0 testing123

Verify client configuration. Ensure that the secret and IP in the client and the FreeRADIUS
server match.

Update FreeRADIUS software. Ensure that you use the latest stable version of FreeRADIUS.

When you are satisfied with your testing and ready to create a production configuration, remove
all the test certificates in /etc/raddb/certs and replace them with your own certificates,
comment out all the test users and clients, and stop radiusd by pressing Ctrl – C . Manage the
radiusd.service with systemctl, just like any other service.

9 Legal Notice
Copyright© 2006–2024 SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the
GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant
Section being this copyright notice and license. A copy of the license version 1.2 is included in
the section entitled “GNU Free Documentation License”.
For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trade-
marks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trade-
marks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.
All information found in this book has been compiled with utmost attention to detail. However,
this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors, nor the
translators shall be held liable for possible errors or the consequences thereof.

9 Setting Up a FreeRADIUS Server

A GNU Free Documentation License
Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor,
Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of
this license document, but changing it is not allowed.

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and useful docu-
ment "free" in the sense of freedom: to assure everyone the effective freedom to copy and redis-
tribute it, with or without modifying it, either commercially or non-commercially. Secondarily,
this License preserves for the author and publisher a way to get credit for their work, while not
being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must
themselves be free in the same sense. It complements the GNU General Public License, which
is a copyleft license designed for free software.
We have designed this License to use it for manuals for free software, because free software needs
free documentation: a free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to software manuals; it can be used for
any textual work, regardless of subject matter or whether it is published as a printed book. We
recommend this License principally for works whose purpose is instruction or reference.

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placed
by the copyright holder saying it can be distributed under the terms of this License. Such a
notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under
the conditions stated herein. The "Document", below, refers to any such manual or work. Any
member of the public is a licensee, and is addressed as "you". You accept the license if you copy,
modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion
of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals
exclusively with the relationship of the publishers or authors of the Document to the Document's
overall subject (or to related matters) and contains nothing that could fall directly within that

10 Setting Up a FreeRADIUS Server

overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section
may not explain any mathematics.) The relationship could be a matter of historical connection
with the subject or with related matters, or of legal, commercial, philosophical, ethical or po-
litical position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being
those of Invariant Sections, in the notice that says that the Document is released under this
License. If a section does not t the above definition of Secondary then it is not allowed to be
designated as Invariant. The Document may contain zero Invariant Sections. If the Document
does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-
Cover Texts, in the notice that says that the Document is released under this License. A Front-
Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format
whose specification is available to the general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of pixels) generic paint
programs or (for drawings) some widely available drawing editor, and that is suitable for input
to text formatters or for automatic translation to a variety of formats suitable for input to text
formatters. A copy made in an otherwise Transparent le format whose markup, or absence of
markup, has been arranged to thwart or discourage subsequent modification by readers is not
Transparent. An image format is not Transparent if used for any substantial amount of text. A
copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Tex-
info input format, LaTeX input format, SGML or XML using a publicly available DTD, and stan-
dard-conforming simple HTML, PostScript or PDF designed for human modification. Examples
of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary
formats that can be read and edited only by proprietary word processors, SGML or XML for
which the DTD and/or processing tools are not generally available, and the machine-generated
HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are
needed to hold, legibly, the material this License requires to appear in the title page. For works
in formats which do not have any title page as such, "Title Page" means the text near the most
prominent appearance of the work's title, preceding the beginning of the body of the text.

11 Setting Up a FreeRADIUS Server

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely
XYZ or contains XYZ in parentheses following text that translates XYZ in another language.
(Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements",
"Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you
modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this Li-
cense applies to the Document. These Warranty Disclaimers are considered to be included by
reference in this License, but only as regards disclaiming warranties: any other implication that
these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or non-com-
mercially, provided that this License, the copyright notices, and the license notice saying this
License applies to the Document are reproduced in all copies, and that you add no other condi-
tions whatsoever to those of this License. You may not use technical measures to obstruct or
control the reading or further copying of the copies you make or distribute. However, you may
accept compensation in exchange for copies. If you distribute a large enough number of copies
you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display
copies.

3. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have printed covers) of the
Document, numbering more than 100, and the Document's license notice requires Cover Texts,
you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-
Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also
clearly and legibly identify you as the publisher of these copies. The front cover must present the
full title with all words of the title equally prominent and visible. You may add other material
on the covers in addition. Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated as verbatim copying in
other respects.

12 Setting Up a FreeRADIUS Server

If the required texts for either cover are too voluminous to t legibly, you should put the rst
ones listed (as many as t reasonably) on the actual cover, and continue the rest onto adjacent
pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must
either include a machine-readable Transparent copy along with each Opaque copy, or state in
or with each Opaque copy a computer-network location from which the general network-using
public has access to download using public-standard network protocols a complete Transparent
copy of the Document, free of added material. If you use the latter option, you must take rea-
sonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that
this Transparent copy will remain thus accessible at the stated location until at least one year
after the last time you distribute an Opaque copy (directly or through your agents or retailers)
of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before
redistributing any large number of copies, to give them a chance to provide you with an updated
version of the Document.

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sec-
tions 2 and 3 above, provided that you release the Modified Version under precisely this License,
with the Modified Version filling the role of the Document, thus licensing distribution and mod-
ification of the Modified Version to whoever possesses a copy of it. In addition, you must do
these things in the Modified Version:

A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document,
and from those of previous versions (which should, if there were any, be listed in the
History section of the Document). You may use the same title as a previous version if the
original publisher of that version gives permission.

B. List on the Title Page, as authors, one or more persons or entities responsible for authorship
of the modifications in the Modified Version, together with at least ve of the principal
authors of the Document (all of its principal authors, if it has fewer than ve), unless they
release you from this requirement.

C. State on the Title page the name of the publisher of the Modified Version, as the publisher.

D. Preserve all the copyright notices of the Document.

13 Setting Up a FreeRADIUS Server

 E. Add an appropriate copyright notice for your modifications adjacent to the other copyright
notices.

F. Include, immediately after the copyright notices, a license notice giving the public permis-
sion to use the Modified Version under the terms of this License, in the form shown in
the Addendum below.

G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts
given in the Document's license notice.

H. Include an unaltered copy of this License.

I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at
least the title, year, new authors, and publisher of the Modified Version as given on the
Title Page. If there is no section Entitled "History" in the Document, create one stating the
title, year, authors, and publisher of the Document as given on its Title Page, then add an
item describing the Modified Version as stated in the previous sentence.

J. Preserve the network location, if any, given in the Document for public access to a Trans-
parent copy of the Document, and likewise the network locations given in the Document
for previous versions it was based on. These may be placed in the "History" section. You
may omit a network location for a work that was published at least four years before the
Document itself, or if the original publisher of the version it refers to gives permission.

K. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the
section, and preserve in the section all the substance and tone of each of the contributor
acknowledgements and/or dedications given therein.

L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their
titles. Section numbers or the equivalent are not considered part of the section titles.

M. Delete any section Entitled "Endorsements". Such a section may not be included in the
Modified Version.

N. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with
any Invariant Section.

O. Preserve any Warranty Disclaimers.

14 Setting Up a FreeRADIUS Server

If the Modified Version includes new front-matter sections or appendices that qualify as Se-
condary Sections and contain no material copied from the Document, you may at your option
designate some or all of these sections as invariant. To do this, add their titles to the list of
Invariant Sections in the Modified Version's license notice. These titles must be distinct from
any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements
of your Modified Version by various parties--for example, statements of peer review or that the
text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to ve words as a Front-Cover Text, and a passage of up to 25
words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only
one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through
arrangements made by) any one entity. If the Document already includes a cover text for the
same cover, previously added by you or by arrangement made by the same entity you are acting
on behalf of, you may not add another; but you may replace the old one, on explicit permission
from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use
their names for publicity for or to assert or imply endorsement of any Modified Version.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the
terms defined in section 4 above for modified versions, provided that you include in the combi-
nation all of the Invariant Sections of all of the original documents, unmodified, and list them
all as Invariant Sections of your combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant
Sections may be replaced with a single copy. If there are multiple Invariant Sections with the
same name but different contents, make the title of each such section unique by adding at the
end of it, in parentheses, the name of the original author or publisher of that section if known,
or else a unique number. Make the same adjustment to the section titles in the list of Invariant
Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original
documents, forming one section Entitled "History"; likewise combine any sections Entitled "Ac-
knowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled
"Endorsements".

15 Setting Up a FreeRADIUS Server

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under
this License, and replace the individual copies of this License in the various documents with a
single copy that is included in the collection, provided that you follow the rules of this License
for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under
this License, provided you insert a copy of this License into the extracted document, and follow
this License in all other respects regarding verbatim copying of that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent docu-
ments or works, in or on a volume of a storage or distribution medium, is called an "aggregate"
if the copyright resulting from the compilation is not used to limit the legal rights of the com-
pilation's users beyond what the individual works permit. When the Document is included in
an aggregate, this License does not apply to the other works in the aggregate which are not
themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if
the Document is less than one half of the entire aggregate, the Document's Cover Texts may be
placed on covers that bracket the Document within the aggregate, or the electronic equivalent
of covers if the Document is in electronic form. Otherwise they must appear on printed covers
that bracket the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Doc-
ument under the terms of section 4. Replacing Invariant Sections with translations requires spe-
cial permission from their copyright holders, but you may include translations of some or all
Invariant Sections in addition to the original versions of these Invariant Sections. You may in-
clude a translation of this License, and all the license notices in the Document, and any War-
ranty Disclaimers, provided that you also include the original English version of this License
and the original versions of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice or disclaimer, the original
version will prevail.

16 Setting Up a FreeRADIUS Server

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the
requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual
title.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided
for under this License. Any other attempt to copy, modify, sublicense or distribute the Document
is void, and will automatically terminate your rights under this License. However, parties who
have received copies, or rights, from you under this License will not have their licenses termi-
nated so long as such parties remain in full compliance.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documenta-
tion License from time to time. Such new versions will be similar in spirit to the present ver-
sion, but may differ in detail to address new problems or concerns. See https://www.gnu.org/
copyleft/ .
Each version of the License is given a distinguishing version number. If the Document specifies
that a particular numbered version of this License "or any later version" applies to it, you have
the option of following the terms and conditions either of that specified version or of any later
version that has been published (not as a draft) by the Free Software Foundation. If the Document
does not specify a version number of this License, you may choose any version ever published
(not as a draft) by the Free Software Foundation.

ADDENDUM: How to use this License for your documents

Copyright (c) YEAR YOUR NAME.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled “GNU
Free Documentation License”.

17 Setting Up a FreeRADIUS Server

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the
“with...Texts.” line with this:

with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three,
merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these
examples in parallel under your choice of free software license, such as the GNU General Public
License, to permit their use in free software.

18 Setting Up a FreeRADIUS Server