Differences

This shows you the differences between two versions of the page.

--- technical:ppsk-meshdesk [2024/04/28 20:11] – system
+++ technical:ppsk-meshdesk [2024/04/28 20:33] (current) – system
@@ Line 96: / Line 96: @@
 ===== MESHdesk Related =====
   * We will change the default PPSK demo mesh network to support Private PSK.
-  *  MQTT is also installed and implemented on our server, which will enable real-time separation of RADIUS users.
+  *  MQTT is also installed and implemented on our server, which will enable real-time termination of RADIUS sessions.
 ==== Change the security of the entry point (SSID) ====
@@ Line 152: / Line 152: @@
 ===== PPSK client session =====
-  * If we try to connect to the PPSK Demo Wireless SSID again, our connection should work as the RADIUS is now done.
+  * If we try to reconnect to the PPSK Demo Wireless SSID, our connection should work because the RADIUS is now complete.
   * Let us take a look at all the places where it is recorded.
 ==== RADIUS Clients ====
-  * The RADIUS Clients applet will indicate when last the client contacted the server.
+  * The RADIUS Clients applet shows when the client last contacted the server.
-  * It will also show the Public IP Address that the RADIUS Client used to connect with.
+  * It also shows the public IP address from which the RADIUS client has connected.
 <panel type="primary">
 {{ :technical:ppsk:radius_client_online.png |}}
 </panel>
-  * With MESHdesk and APdesk we use a convention of {m|a}[_hosta_]{Mesh ID/AP Profile ID}[_]{Entry ID/SSID ID}
+  * For MESHdesk and APdesk we use the convention {m|a}[_hosta_]{Mesh ID/AP Profile ID}[_]{Entry ID/SSID ID}
-  * In order for RADIUSdesk to know which AP or mesh node to contact to disconnect a user from the WiFi, we also record extra information from the accounting data sent by hostapd.
+  * We also record additional information from the accounting data sent by hostapd so that RADIUSdesk knows which AP or mesh node it needs to contact to disconnect a user from the WiFi.
 ==== Activity Monitor ====
-  * Under Activity Monitor you can view activeand historical sessions.
+  * Under Activity Monitor you can view active and historical sessions.
-  * You can also terminate active sessions.
+  * You can also end active sessions
 <panel type="primary">
 {{ :technical:ppsk:permanent_session.png |}}
 </panel>
-  * Here you can see where we terminated the active session and the user's device then moved to another radio automatically. (Notice the value of Operator Name is different)
+  * Here you can see where we ended the active session and the user's device then automatically switched to another radio. (Note that the value of Operator Name is different)
 <panel type="primary">
 {{ :technical:ppsk:permanent_session_kick.png |}}
@@ Line 176: / Line 176: @@
 ==== Usage graph ====
-  * We can also view the usage graph of the user.
+  * We can also look at the user's usage graph.
-  * Here we can see that the usage are just over 1 GB which means the system then took action and disconnected the user's device.
+  * Here we can see that the usage is just over 1 GB, which means that the system has then disconnected from the user's device.
 <panel type="primary">
 {{ :technical:ppsk:graph.png |}}
@@ Line 183: / Line 183: @@
 ==== Life on VLAN 105 ====
-  * After the user's phone was disconnected from the main network, it reconnected but this time it was now moved to VLAN 105, the captive portal.
+  * After the user's phone was disconnected from the main network, it was reconnected, but this time it was moved to VLAN 105, the captive portal.
 <panel type="primary">
 {{ :technical:ppsk:captive_p.jpeg |}}