Differences

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

--- technical:ppsk-meshdesk [2024/04/28 18:06] – 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 114: / Line 114: @@
 ==== Add VLAN 105 to Captive Portal ====
-  * The wizard already created and Captive Portal exit point for us.
+  * The wizard has already created a Captive Portal exit point for us.
   * We can simply connect it to VLAN 105.
-  * This means that traffic from the open SSID as well as traffic from VLAN 105 will hit the Captive Portal and be presented with a login page.
+  * This means that both the traffic from the open SSID and the traffic from VLAN 105 will hit the captive portal and a login page will be displayed.
 <panel type="primary">
 {{ :technical:ppsk:md_ppsk_exit.png |}}
 </panel>
-  * Everything is now in place on the mesh network for the PPSK to work and we can start to add nodes to the mesh network.
+  * Now that  the mesh network is all set up for PPSK to work, we can start adding nodes to the mesh network.
-  * After we added a mesh nodes we can try to connect to the **PPSK Demo Wireless** SSID with the key of **11223344**
+  * After we have added a mesh node, we can try to connect to the **PPSK Demo Wireless** SSID with the key **11223344**
-  * If will fail first since we have not yet did the final step which is to add it as a RADIUS client.
+  * This will initially fail as we have not yet performed the final step of adding as a RADIUS client.
 ----------
-===== RADIUS Related (Final) =====
+===== RADIUS related (final) =====
-==== Add RADIUS Client ====
+==== Add RADIUS client ====
   * Go to **RADIUS** -> **RADIUS Clients** and click on the **New Arrivals** button (The one with the car icon).
-  * This should list the hotsapd program's info from the mesh node on which you tried to connect to.
+  * This should list the hotsapd program's info from the Mesh node you have tried to connect to.
 <panel type="primary">
 {{ :technical:ppsk:radius_arrival.png |}}
 </panel>
-  * Click on the **Attach** button to show the Add Window.
+  * Click the **Attach** button to display the Add window.
 <panel type="primary">
 {{ :technical:ppsk:radius_attach1.png |}}
 </panel>
-  * Make sure you select only the **PPSK Demo** realm.
+  * Make sure that you only select the **PPSK Demo** realm.
 <panel type="primary">
 {{ :technical:ppsk:radius_attach2.png |}}
 </panel>
-  * After you attached it, there is one last bit and then we're done.
+  * After you have attached it, there is one last step and then we are done.
-  * Edit the RADIUS Client and specify the type as **Private PSK**.
+  * Edit the RADIUS client and specify **Private PSK** as the type.
 <panel type="primary">
 {{ :technical:ppsk:radius_edit.png |}}
 </panel>
-  * We use the info we recorded when we modified the mesh network entry point (SSID)
+  * We use the information we recorded when we changed the mesh network entry point (SSID)
-  * Everything is now complete and in place for us to enjoy the fruit of our labour.
+  * Now everything is ready and we can enjoy the fruits of our labour.
 ------
-==== PPSK client session ====
+===== PPSK client session =====
-  * When we try to connect again to the PPSK Demo Wireless SSID, our connection should go through since the RADIUS has now been taken care of.
+  * If we try to reconnect to the PPSK Demo Wireless SSID, our connection should work because the RADIUS is now complete.
-  * Lets see all the places where it is recorded.
+  * Let us take a look at all the places where it is recorded.
+==== RADIUS Clients ====
+  * The RADIUS Clients applet shows when the client last contacted the server.
+  * It also shows the public IP address from which the RADIUS client has connected.
+<panel type="primary">
+{{ :technical:ppsk:radius_client_online.png |}}
+</panel>
+  * For MESHdesk and APdesk we use the convention {m|a}[_hosta_]{Mesh ID/AP Profile ID}[_]{Entry ID/SSID ID}
+  * 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 active and historical sessions.
+  * You can also end active sessions
+<panel type="primary">
+{{ :technical:ppsk:permanent_session.png |}}
+</panel>
+  * 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 |}}
+</panel>
+==== Usage graph ====
+  * We can also look at the user's usage graph.
+  * 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 |}}
+</panel>
+==== Life on VLAN 105 ====
+  * 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 |}}
+</panel>