This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
technical:ppp-meshdesk [2023/11/19 19:33] admin [POC using a $15 AP] |
technical:ppp-meshdesk [2023/11/20 07:36] (current) admin [Load on PPPoE server] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Accel-ppp on OpenWrt with MESHdesk ====== | ====== Accel-ppp on OpenWrt with MESHdesk ====== | ||
===== Background ===== | ===== Background ===== | ||
- | * One of the primary | + | * One of the main goals of MESHdesk is to enable fast WiFi deployment |
- | * Another goal is the ability to manage | + | * 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 |
* An alternative to a captive portal is PPPoE. | * An alternative to a captive portal is PPPoE. | ||
- | * We introduced PPPoE client support in MESHdesk and APdesk | + | * In 2021 we introduced PPPoE client support in MESHdesk and APdesk. |
* PPPoE is used by most WISPs. | * PPPoE is used by most WISPs. | ||
- | * In South Africa (and probably most other countries) the PPPoE server of choice is provided by Mikrotik' | + | * In South Africa (and probably |
- | * This is combined with the CPE of choice (Which is typically | + | * This is combined with the CPE of choice (usually |
- | * There is already a rock solid and feature rich Open Source | + | * There is already a solid and feature-rich open source |
- | * Being a firm believer | + | * As we strongly believe |
- | * We just needed to get **Accel-ppp** compiled | + | * The biggest hurdle was compiling |
- | * Thereafter | + | * 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 tap into this knowledge and develop this last missing piece of the puzzle. | + | * This was no easy task but thanks to the work that others |
- | * With this part completed | + | * Now that this part is complete |
===== POC using a $15 AP ===== | ===== POC using a $15 AP ===== | ||
- | * With fishing | + | * 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 on the hardware. | + | * For this Proof Of Concept (POC), we decided to go light on the hardware |
- | * The Xiaomi 4C were on special so we grabbed a couple of them. | + | * The Xiaomi 4C was on special |
- | * The special' | + | * The price of the special offer was equivalent |
{{: | {{: | ||
<WRAP center round info 100%> | <WRAP center round info 100%> | ||
* MESHdesk and APdesk support WiFi 6 and hardware with up to three radios. | * MESHdesk and APdesk support WiFi 6 and hardware with up to three radios. | ||
- | * We deliberately | + | * We have deliberately |
</ | </ | ||
+ | * Here are the technical details of the AP: | ||
+ | |||
+ | ^ Model ^ SoC ^CPU MHz ^Flash MB ^RAM MB ^WLAN Hardware | ||
+ | | Mi Router 4C | MediaTek MT7628AN |580 |16 |64 | ||
===== POC networks | ===== POC networks | ||
Line 39: | Line 43: | ||
* This connects then with the **Jhb-South Wireless** SSID | * This connects then with the **Jhb-South Wireless** SSID | ||
{{: | {{: | ||
- | * Jhb-South will be our main mesh network | + | * Jhb-South will be our main mesh network |
==== Client Mesh Networks ==== | ==== Client Mesh Networks ==== | ||
- | * We create two client mesh networks | + | * We create two client mesh networks |
* These can typically be a unit in a gated community. | * These can typically be a unit in a gated community. | ||
{{: | {{: | ||
==== PPPoE RADIUS users ==== | ==== PPPoE RADIUS users ==== | ||
- | * We create | + | * We create |
- | * Since Accel-ppp can serve as a drop in replacement | + | * Since Accel-ppp can serve as replacement |
* Accel-ppp will interpret them and apply the desired shaping. | * Accel-ppp will interpret them and apply the desired shaping. | ||
<WRAP center round tip 100%> | <WRAP center round tip 100%> | ||
- | * Accel-ppp also support | + | * Accel-ppp also supports the advanced shaping |
- | * 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. |
</ | </ | ||
{{: | {{: | ||
==== Add gateway nodes to client networks ==== | ==== Add gateway nodes to client networks ==== | ||
- | * We add gateway nodes to out client networks. | + | * We add gateway nodes to our client networks. |
- | * We specify their Internet Connection as **WiFi Client - PPPoE** and give the required | + | * We specify their Internet Connection as **WiFi Client - PPPoE** and provide |
{{: | {{: | ||
==== Up and running overview ==== | ==== Up and running overview ==== | ||
- | * Once the client gateway nodes have been added we can now view all everything in one grid. | + | * Now that the client gateway nodes have been added, we can display |
{{: | {{: | ||
- | * A few important points | + | * A few important points |
* The Jhb-South mesh has two nodes: PPPoE-GW and Node-2. | * The Jhb-South mesh has two nodes: PPPoE-GW and Node-2. | ||
- | * The Internet connection for PPPoE-GW is using Ethernet (LAN). | + | * The Internet connection for PPPoE-GW is via Ethernet (LAN). |
* The Internet connection for Node-2 is the mesh. | * The Internet connection for Node-2 is the mesh. | ||
- | * The Nodes in the client networks | + | * The nodes in the client networks |
- | * Although not shown here, the one client AP is connected to PPPoE-GW's WiFi. The other client AP is connected to Node-2's WiFi. | + | * 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. |
{{: | {{: | ||
<WRAP center round tip 100%> | <WRAP center round tip 100%> | ||
- | Should the need arise to expand | + | If it is necessary |
</ | </ | ||
Line 80: | Line 83: | ||
* Finally we show the active sessions of Unit1 and Unit2 in RADIUS | * Finally we show the active sessions of Unit1 and Unit2 in RADIUS | ||
{{: | {{: | ||
- | * Since this is a drop in replacement for Mikrotik | + | * Since this is a replacement for Mikrotik, the extended |
* http:// | * http:// | ||
+ | |||
+ | ==== 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. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | * Our PPPoE clients are limited to 2Mbps up and down. | ||
+ | |||
+ | {{: | ||