Differences

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

--- technical:ppp-meshdesk [2023/11/19 19:08]
admin [PPPoE RADIUS Users]
+++ technical:ppp-meshdesk [2023/11/20 07:36] (current)
admin [Load on PPPoE server]
@@ Line 1: / Line 1: @@
 ====== Accel-ppp on OpenWrt with MESHdesk ======
 ===== Background =====
-  * One of the primary goals of MESHdesk is to allow rapid WiFi deployment using Commercial off-the-shelf (COTS) hardware with Open Source firmware.
+  * One of the main goals of MESHdesk is to enable fast WiFi deployment with commercial off-the-shelf (COTS) hardware and open source firmware.
-  * Another goal is the ability to manage the network usage.
+  * Another goal is the ability to manage network usage.
-  * For bandwidth and data usage we include a captive portal.
+  * For **bandwidth** and **data usage**  management we include a captive portal.
   * An alternative to a captive portal is PPPoE.
-  * We introduced PPPoE client support in MESHdesk and APdesk around 2021.
+  * In 2021 we introduced PPPoE client support in MESHdesk and APdesk.
   * PPPoE is used by most WISPs.
-     * In South Africa (and probably most other countries) the PPPoE server of choice is provided by Mikrotik's RouterOS.
+     * In South Africa (and probably in most other countries) the PPPoE server of choice is provided by Mikrotik's RouterOS.
-     * This is combined with the CPE of choice (Which is typically Ubiquiti).
+     * This is combined with the CPE of choice (usually Ubiquiti).
-  * There is already a rock solid and feature rich Open Source PPPoE server called **Accel-ppp** available for Linux.
+  * There is already a solid and feature-rich open source PPPoE server called **Accel-ppp** for Linux.
-  * Being a firm believer in Open Source we aim to provide a fully Open Source system, end-to-end, for Internet providers.
+  * As we strongly believe in open source we want to offer a completely open source system for Internet providers.
-  * We just needed to get **Accel-ppp** compiled and running on OpenWrt.
+  * The biggest hurdle was compiling Accel-ppp and getting it to run under OpenWrt.
-  * Thereafter to integrate it with MESHdesk and APdesk.
+  * Then we had to integrate it with MESHdesk and APdesk.
-  * This was no small task but thanks to the work done by others in the past we could develop this last missing piece of the puzzle.
+  * This was no easy task but thanks to the work that others have done in the past we were able to draw on this knowledge and develop this last missing piece of the puzzle.
-  * With this part completed we can offer Internet providers a managed alternative which could serve as a drop-in replacement for their current vendor specific PPPoE servers.
+  * Now that this part is complete we can offer Internet providers a managed alternative that could serve as a drop-in replacement for their current vendor-specific PPPoE servers.
 ===== POC using a $15 AP  =====
-  * I like fishing and its much more fun to catch a big fish using a light line.
+  * When fishing, it is much more fun to catch a big fish with a light line.
-  * For this Proof Of Concept (POC) we decided to also go light with the hardware.
+  * For this Proof Of Concept (POC), we decided to go light on the hardware too.
-  * The Xiaomi 4C were on special so we grabbed a couple of them.
+  * The Xiaomi 4C was on special offer, so we grabbed a couple of them.
-  * The special's price equate to ~15USD per device.
+  * The price of the special offer was equivalent to ~15USD per device.
 {{:technical:pppoe:4c_special.png|}}
 <WRAP center round info 100%>
   * MESHdesk and APdesk support WiFi 6 and hardware with up to three radios.
-  * We deliberately choose entry level hardware for this POC to proof a point.
+  * We have deliberately chosen entry-level hardware for this POC to prove a point.
 </WRAP>
+  * Here are the technical details of the AP:
+^ Model  ^ SoC  ^CPU MHz  ^Flash MB  ^RAM MB  ^WLAN Hardware  ^WLAN2.4  ^WLAN5.0  ^100M ports  ^
+| Mi Router 4C | MediaTek MT7628AN	|580 |16	|64  |MT7628AN  |b/g/n  |-	|3 |
 ===== POC networks  =====
@@ Line 39: / Line 43: @@
         * This connects then with the **Jhb-South Wireless** SSID
 {{:technical:pppoe:ppp_poc_mesh_exit.png|}}
-  * Jhb-South will be our main mesh network where various APs will connect to using WiFi and PPPoE.
+  * Jhb-South will be our main mesh network to which various APs will connect via WiFi and PPPoE.
 ==== Client Mesh Networks ====
-  * We create two client mesh networks called **Jhb-South-Unit1** and **Jhb-South-Unit2**.
+  * We create two client mesh networks named **Jhb-South-Unit1** and **Jhb-South-Unit2**.
   * These can typically be a unit in a gated community.
 {{:technical:pppoe:ppp_poc_mesh.png|}}
-==== PPPoE RADIUS Users ====
+==== PPPoE RADIUS users ====
-  * We create Permanent Users which will be used by the gateway AP of the Client Mesh Networks.
+  * We create permanent users that are used by the gateway AP of the client mesh networks.
-  * Since Accel-ppp can serve as a drop in replacement to Mikrotik we can use the old Mikrotik attributes as is.
+  * Since Accel-ppp can serve as replacement for Mikrotik, we can use the old Mikrotik attributes as they are.
   * Accel-ppp will interpret them and apply the desired shaping.
 <WRAP center round tip 100%>
-  * Accel-ppp also support advanced shaping features that the Mikrotik PPPoE server do like bursting.
+  * Accel-ppp also supports the advanced shaping functions that the Mikrotik PPPoE server do such as bursting.
-  * Again no need to change any of the current Mikrotik reply attributes from RADIUS. It will interpret and apply even the advanced Mikrotik reply values.
+  * Again, there is no need to change any of the current Mikrotik reply attributes from RADIUS. It will interpret and apply even the advanced Mikrotik reply values.
 </WRAP>
 {{:technical:pppoe:ppp_poc_pppoe_mikrotik.png|}}
+==== Add gateway nodes to client networks ====
+  * We add gateway nodes to our client networks.
+  * We specify their Internet Connection as **WiFi Client - PPPoE** and provide the required information.
+{{:technical:pppoe:ppp_poc_pppoe_client.png|}}
+==== Up and running overview ====
+  * Now that the client gateway nodes have been added, we can display everything in a grid.
+{{:technical:pppoe:ppp_poc_nodes.png?nolink|}}
+  * A few important points about the screenshot above.
+  * The Jhb-South mesh has two nodes: PPPoE-GW and Node-2.
+  * The Internet connection for PPPoE-GW is via Ethernet (LAN).
+  * The Internet connection for Node-2 is the mesh.
+  * The nodes in the client networks use WiFi for the Internet (WiFi with PPPoE)
+  * Although not shown here, one client AP is connected to the WiFi of the PPPoE-GW. The other client AP is connected to the WiFi of Node-2.
+{{:technical:pppoe:ppp_poc_mesh.png?nolink|}}
+<WRAP center round tip 100%>
+If it is necessary to extend the coverage of the client networks (Unit1 and Unit2), you can simply add more mesh nodes to the client networks.
+</WRAP>
+==== RADIUS Activity ====
+  * Finally we show the active sessions of Unit1 and Unit2 in RADIUS
+{{:technical:pppoe:ppp_poc_pppoe_users.png?nolink|}}
+  * Since this is a replacement for Mikrotik, the extended RADIUSdesk functions such as FUP also work on the Accel-ppp PPPoE server.
+  * http://radiusdesk.com/wiki/radiusdesk/profiles/fup
+==== Load on PPPoE server ====
+  * We deliberately chose low-end hardware, and although we did not perform any stress tests, the memory and CPU utilization of the node running Accel-ppp looks very good, even when the two client APs are streaming Youtube.
+{{:technical:pppoe:ppp_poc_load.png?nolink|}}
+  * Our PPPoE clients are limited to 2Mbps up and down.
+{{:technical:pppoe:ppp_poc_sessions.png?nolink|}}

RADIUSdesk

Page Tools

Site Tools

User Tools

Differences