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 20:15] admin [Client Mesh Networks] |
technical:ppp-meshdesk [2023/11/20 07:36] (current) admin [Load on PPPoE server] |
||
---|---|---|---|
Line 13: | Line 13: | ||
* There is already a solid and feature-rich open source PPPoE server called **Accel-ppp** for Linux. | * There is already a solid and feature-rich open source PPPoE server called **Accel-ppp** for Linux. | ||
* As we strongly believe in open source we want to offer a completely open source system for Internet providers. | * As we strongly believe in open source we want to offer a completely open source system for Internet providers. | ||
- | * We just had to compile | + | * The biggest hurdle was compiling |
* Then we had to integrate it with MESHdesk and APdesk. | * Then we had to integrate it with MESHdesk and APdesk. | ||
* 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. | * 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. | ||
Line 29: | Line 29: | ||
* We have deliberately chosen entry-level hardware for this POC to prove a point. | * We have deliberately chosen entry-level hardware for this POC to prove a point. | ||
</ | </ | ||
+ | * 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 46: | Line 50: | ||
==== 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 79: | 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, the advanced | + | * 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. | ||
+ | |||
+ | {{: | ||