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 [2024/02/19 10:18] systemtechnical:ppp-meshdesk [2024/02/19 10:32] (current) system
Line 1: Line 1:
 +<nav type="pills" justified="false">
 +  * [[:user_manuals|Back to Documentation]]
 +  * [[:technical:ppp-meshdesk|Accel-ppp on OpenWrt]]
 +</nav>
 +
 +-----
 ====== Accel-ppp on OpenWrt with MESHdesk ====== ====== Accel-ppp on OpenWrt with MESHdesk ======
 ===== Background ===== ===== Background =====
Line 22: Line 28:
   * The Xiaomi 4C was on special offer, so we grabbed a couple of them.   * The Xiaomi 4C was on special offer, so we grabbed a couple of them.
   * The price of the special offer was ~15USD per device.   * The price of the special offer was ~15USD per device.
 +<panel type="primary">
 {{:technical:pppoe:4c_special.png|}} {{:technical:pppoe:4c_special.png|}}
 +</panel>
  
-<WRAP center round info 100%>+<alert type="info">
   * 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 purposely chose entry-level hardware for this POC to prove a point.   * We purposely chose entry-level hardware for this POC to prove a point.
-</WRAP>+</alert>
   * Here are the technical details of the AP:   * Here are the technical details of the AP:
 +<panel type="primary" title="Device Hardware" no-body="true">
 ^ Model  ^ SoC  ^CPU MHz  ^Flash MB  ^RAM MB  ^WLAN Hardware  ^WLAN2.4  ^WLAN5.0  ^100M ports  ^ ^ 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 | | Mi Router 4C | MediaTek MT7628AN |580 |16 |64  |MT7628AN  |b/g/ |- |3 |
 +</panel>
 ===== POC networks  ===== ===== POC networks  =====
 ==== Jhb-South (Main Mesh) ==== ==== Jhb-South (Main Mesh) ====
Line 41: Line 49:
         * Add a PPPoE server exit point.         * Add a PPPoE server exit point.
         * This connects then with the **Jhb-South Wireless** SSID         * This connects then with the **Jhb-South Wireless** SSID
 +<panel type="primary">
 {{:technical:pppoe:ppp_poc_mesh_exit.png|}} {{:technical:pppoe:ppp_poc_mesh_exit.png|}}
 +</panel>
   * Jhb-South will be our main mesh network to which various APs will connect via WiFi and PPPoE.   * Jhb-South will be our main mesh network to which various APs will connect via WiFi and PPPoE.
 ==== Client Mesh Networks ==== ==== Client Mesh Networks ====
   * We create two client mesh networks named **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.   * These can typically be a unit in a gated community.
 +<panel type="primary">
 {{:technical:pppoe:ppp_poc_mesh.png|}} {{:technical:pppoe:ppp_poc_mesh.png|}}
 +</panel>
  
 ==== PPPoE RADIUS users ==== ==== PPPoE RADIUS users ====
Line 52: Line 64:
   * Since Accel-ppp can serve as replacement for Mikrotik, we can use the old Mikrotik attributes as they are.   * 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.   * Accel-ppp will interpret them and apply the desired shaping.
-<WRAP center round tip 100%>+<alert type="info">
   * Accel-ppp also supports the advanced shaping features of the Mikrotik PPPoE server, such as bursting.   * Accel-ppp also supports the advanced shaping features of the Mikrotik PPPoE server, such as bursting.
   * Again, it is not necessary to change the current Mikrotik reply attributes from RADIUS. It even interprets and uses the advanced Mikrotik reply values.   * Again, it is not necessary to change the current Mikrotik reply attributes from RADIUS. It even interprets and uses the advanced Mikrotik reply values.
-</WRAP>+</alert> 
 +<panel type="primary">
 {{:technical:pppoe:ppp_poc_pppoe_mikrotik.png|}} {{:technical:pppoe:ppp_poc_pppoe_mikrotik.png|}}
 +</panel>
  
 ==== Add gateway nodes to client networks ==== ==== Add gateway nodes to client networks ====
   * We add gateway nodes to our client networks.   * We add gateway nodes to our client networks.
   * We specify their Internet Connection as **WiFi Client - PPPoE** and provide the required information.   * We specify their Internet Connection as **WiFi Client - PPPoE** and provide the required information.
 +<panel type="primary">
 {{:technical:pppoe:ppp_poc_pppoe_client.png|}} {{:technical:pppoe:ppp_poc_pppoe_client.png|}}
 +</panel>
 ==== Up and running overview ==== ==== Up and running overview ====
   * Now that the client gateway nodes have been added, we can display everything in a grid.   * Now that the client gateway nodes have been added, we can display everything in a grid.
 +<panel type="primary">
 {{:technical:pppoe:ppp_poc_nodes.png?nolink|}} {{:technical:pppoe:ppp_poc_nodes.png?nolink|}}
 +</panel>
   * A few important points about the screenshot 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.
Line 73: Line 90:
   * 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.   * 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.
  
 +<panel type="primary">
 {{:technical:pppoe:ppp_poc_mesh.png?nolink|}} {{:technical:pppoe:ppp_poc_mesh.png?nolink|}}
 +</panel>
  
-<WRAP center round tip 100%>+<alert type="info">
 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. 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>+</alert>
  
 ==== RADIUS Activity ==== ==== RADIUS Activity ====
   * Finally we show the active sessions of Unit1 and Unit2 in RADIUS   * Finally we show the active sessions of Unit1 and Unit2 in RADIUS
 +<panel type="primary">
 {{:technical:pppoe:ppp_poc_pppoe_users.png?nolink|}} {{:technical:pppoe:ppp_poc_pppoe_users.png?nolink|}}
 +</panel>
   * Since this is a replacement for Mikrotik, the extended RADIUSdesk functions such as FUP 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
Line 87: Line 108:
 ==== Load on PPPoE server ==== ==== Load on PPPoE server ====
   * We deliberately opted for low-end hardware, and although we did not perform any stress tests, the memory and CPU utilisation of the node running Accel-ppp looks very good, even when the two client APs are streaming Youtube.   * We deliberately opted for low-end hardware, and although we did not perform any stress tests, the memory and CPU utilisation of the node running Accel-ppp looks very good, even when the two client APs are streaming Youtube.
 +<panel type="primary">
 {{:technical:pppoe:ppp_poc_load.png?nolink|}} {{:technical:pppoe:ppp_poc_load.png?nolink|}}
 +</panel>
  
   * Our PPPoE clients are limited to 2Mbps up and down.   * Our PPPoE clients are limited to 2Mbps up and down.
 +<panel type="primary">
 {{:technical:pppoe:ppp_poc_sessions.png?nolink|}} {{:technical:pppoe:ppp_poc_sessions.png?nolink|}}
 +</panel>
  
  
  • technical/ppp-meshdesk.1708330726.txt.gz
  • Last modified: 2024/02/19 10:18
  • by system