RADIUSdesk

logo

Differences

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

Link to this comparison view

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 Accel-ppp and get it running under OpenWrt.+  * The biggest hurdle was compiling Accel-ppp and getting it to run under OpenWrt.
   * 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.
 </WRAP> </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/ |- |3 |
  
 ===== POC networks  ===== ===== POC networks  =====
Line 46: Line 50:
  
 ==== 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 Mikrotikwe can use the old Mikrotik attributes as they are.
   * 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 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> </WRAP>
 {{:technical:pppoe:ppp_poc_pppoe_mikrotik.png|}} {{:technical:pppoe:ppp_poc_pppoe_mikrotik.png|}}
  
 ==== 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 detail.+  * We specify their Internet Connection as **WiFi Client - PPPoE** and provide the required information.
 {{:technical:pppoe:ppp_poc_pppoe_client.png|}} {{:technical:pppoe:ppp_poc_pppoe_client.png|}}
  
 ==== 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 addedwe can display everything in grid.
 {{:technical:pppoe:ppp_poc_nodes.png?nolink|}} {{:technical:pppoe:ppp_poc_nodes.png?nolink|}}
-  * A few important points on the sceenshot above.+  * A few important points about the screenshot above.
   * 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 are using WiFi for Internet (WiFi with PPPoE) +  * The nodes in the client networks use WiFi for the Internet (WiFi with PPPoE) 
-  * 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.
  
 {{:technical:pppoe:ppp_poc_mesh.png?nolink|}} {{:technical:pppoe:ppp_poc_mesh.png?nolink|}}
  
 <WRAP center round tip 100%> <WRAP center round tip 100%>
-Should the need arise to expand the coverage of the client networks (Unit1 and Unit2), you can simply add more mesh nodes to the client networks.+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> </WRAP>
  
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
 {{:technical:pppoe:ppp_poc_pppoe_users.png?nolink|}} {{:technical:pppoe:ppp_poc_pppoe_users.png?nolink|}}
-  * Since this is a drop in replacement for Mikrotik, the advanced RADIUSdesk features like FUP will also work on the Accel-ppp PPPoE server.+  * 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   * 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|}}