Updated.

Author: harneshalaka

tasks/freeradius-setup-server-add-client-user.xml

@@ -24,7 +24,7 @@ in the assembly -->
       <para>
         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 file and the clients are added in the client configuration file. These configuration files are stored on the server where FreeRADIUS is installed.
       </para>
-      <para>The machines that can use the devices of the FreeRADIUS server are defined in the <filename>client.conf</filename> file.</para>
+      <para>The machines that can use the devices of the FreeRADIUS server are defined in the <filename>/etc/raddb/clients.conf</filename> file.</para>
     </abstract>
   </info>
   <procedure xml:id="add-client-user"><title>Configuring users and clients</title>
@@ -38,9 +38,9 @@ in the assembly -->
     Service-Type = New-User,
     Framed-IP-Address = 190.155.2.50</screen></step>
   <step>
-    <para>Add a test client and user to test the authentication in <filename>/etc/raddb/client.conf</filename>.</para>
-    <screen>vi /etc/raddb/client.conf</screen>
-    <para>A test client, localhost, is provided in <filename>/etc/raddb/client.conf</filename>, with the secret <literal>testing123</literal>.</para>
+    <para>Add a test client and user to test the authentication in <filename>/etc/raddb/clients.conf</filename>.</para>
+    <screen>&prompt.sudo; vi /etc/raddb/clients.conf</screen>
+    <para>A test client, localhost, is provided in <filename>/etc/raddb/clients.conf</filename>, with the secret <literal>testing123</literal>.</para>
     <screen>client private-networks {
       ipaddr          = 190.1.0/22
       secret          = testingabc-1
@@ -53,7 +53,7 @@ in the assembly -->
   </step><step>
 <para>Add clients of the RADIUS server, such as a wireless access point, network switch, or another form of NAS.</para>
 <para>Create a client configuration on your server by using the following example.</para>
-<para>Uncomment the following entry in <filename>/etc/raddb/client.conf</filename> and use the IP address of your test client machine or access gateway instead of the given IP address.</para>
+<para>Uncomment the following entry in <filename>/etc/raddb/clients.conf</filename> and use the IP address of your test client machine or access gateway instead of the given IP address.</para>
 <screen>client private-network-1 {
 ipaddr          = 192.0.2.0/24
 secret          = testing123-1
@@ -62,9 +62,9 @@ secret          = testing123-1
 </step>
 <step>
 <para>On the client machine, install <command>freeradius-server-utils</command>. </para>
-<screen>&prompt.sudo;sudo zypper install freeradius-server and freeradius-server-utils</screen>
+<screen>&prompt.sudo; zypper install freeradius-server freeradius-server-utils</screen>
 </step>
  </procedure>
- <para>You can now add more users and configure databases. </para>
+ <para>You can now add more users and configure database. </para>
   <para>Run one more login test from a different computer on your network. </para>
 </topic>

tasks/freeradius-setup-server-create-test-certificates.xml

@@ -23,7 +23,7 @@ in the assembly -->
     <abstract><!-- can be changed via merge in the assembly -->
       <para>Certificates enable secure communication between the FreeRADIUS clients and the FreeRADIUS server.</para>
       <para>
-        To allow access to the server, certificate authentication is required. To test the authentication using FreeRADIUS, you can create test certificates. The following example shows how to create test certificates to test FreeRADIUS. Ensure that you remove the test certificates and use the correct certificates after testing FreeRADIUS.</para>
+        To allow access to the server, certificate authentication is required. To test the authentication using FreeRADIUS, you can create test certificates. The following example shows how to create test certificates to test FreeRADIUS. Ensure that you remove the test certificates created for testing and use the correct certificates after testing FreeRADIUS.</para>
       <note><para>The test certificates created are not suitable for production use.</para></note>
     </abstract>
   </info>

tasks/freeradius-setup-server-start-freeradius.xml

@@ -22,8 +22,7 @@ in the assembly -->
     <meta name="maintainer" content="[email protected]" its:translate="no"/>
     <abstract><!-- can be changed via merge in the assembly -->
       <para>
-        After adding client and user, you must start the FreeRADIUS daemon.
-      </para>
+        After adding client and user, you must start the FreeRADIUS daemon.</para>
     </abstract>
   </info>
   <procedure xml:id="start-freeradius"><title>Starting the FreeRADIUS daemon</title>

tasks/freeradius-setup-server-start-server.xml

@@ -22,15 +22,14 @@ in the assembly -->
     <meta name="maintainer" content="[email protected]" its:translate="no"/>
     <abstract><!-- can be changed via merge in the assembly -->
       <para>
-        You must start FreeRADIUS on the server after installation.
+        You must start FreeRADIUS on the server after installation. For testing, after creating bootstrap, start the FreeRADIUS server in debugging mode.
       </para>
     </abstract>
   </info>  
   <procedure xml:id="freeradius-setup-server-start-freeradius-server"><title>Starting FreeRADIUS</title>
     <para>After the bootstrap is complete, start the server in debugging mode as a <literal>root</literal> user.</para>
   <step>
-    <para>To do this, run the following command:</para>
-  <note><para>Start the FreeRADIUS server in debugging mode only for testing. Other than for testing, use <command>sudo systemctl start freeradius</command></para></note>
+  <note><para>Start the FreeRADIUS server in debugging mode only for testing. Other than for testing, use <command>&prompt.sudo; systemctl start freeradius</command></para></note>
 
     <screen>&prompt.sudo; radiusd -X
       [...]
@@ -43,6 +42,6 @@ in the assembly -->
       Listening on proxy address :: port 58415
       Ready to process requests</screen>
       <para>The <literal>Listening</literal> and <literal>Ready to process requests</literal> appear when the server starts correctly.</para>
-  </step>
+   </step>
  </procedure>
 </topic>