Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
technical:ppp-rd-agent [2023/11/07 20:38] admin [Startup and config file] |
technical:ppp-rd-agent [2023/11/08 10:30] (current) admin [Startup and config reference files] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== RADIUSdesk Accel-ppp Agent ====== | ====== RADIUSdesk Accel-ppp Agent ====== | ||
| ===== Overview ===== | ===== Overview ===== | ||
| - | * The **RADIUSdesk | + | * The **RADIUSdesk |
| * It uses a couple of Lua based libraries and scripts to fulfill its mandate. | * It uses a couple of Lua based libraries and scripts to fulfill its mandate. | ||
| Line 16: | Line 16: | ||
| ==== The Rest ==== | ==== The Rest ==== | ||
| - | * We assume you already have a device that has Acell-ppp installed as per instructions elsewhere on this Wiki. | + | * We assume you already have a device that has Accel-ppp installed as per instructions elsewhere on this Wiki. |
| * Install the following packages. | * Install the following packages. | ||
| <code bash> | <code bash> | ||
| Line 63: | Line 63: | ||
| * We also specify the interface we want the PPPoE service to run on. | * We also specify the interface we want the PPPoE service to run on. | ||
| * In our case we have a Raspberry Pi 4 with an Enternet port (eth0) where we will run the PPPoE service on. | * In our case we have a Raspberry Pi 4 with an Enternet port (eth0) where we will run the PPPoE service on. | ||
| - | * The agent will then fetch the MAC Address of this interface and forward the request for config | + | * The agent will then fetch the MAC Address of this interface and forward the request for config |
| * Make changes to this file so that it works with your environment and device. | * Make changes to this file so that it works with your environment and device. | ||
| === Startup File === | === Startup File === | ||
| + | * Disable automatic startup of Accel-ppp. | ||
| + | <code bash> | ||
| + | sudo systemctl disable accel-ppp | ||
| + | </ | ||
| * The startup file is /// | * The startup file is /// | ||
| * You also have to tweak it to work on the device running the RADIUSdesk Accel-ppp Agent. | * You also have to tweak it to work on the device running the RADIUSdesk Accel-ppp Agent. | ||
| Line 87: | Line 91: | ||
| * Make sure that your setup matches your device' | * Make sure that your setup matches your device' | ||
| - | <WRAP center round info 90%> | + | <WRAP center round info 100%> |
| Since PPPoE works on Layer2, you can have both the PPPoE and the WAN connection on one physical interface e.g eth0 in our case with the Pi. | Since PPPoE works on Layer2, you can have both the PPPoE and the WAN connection on one physical interface e.g eth0 in our case with the Pi. | ||
| </ | </ | ||
| + | * On the Raspberry Pi the rc.local script was called automatically during startup. | ||
| + | * On Ubuntu you'll probably have to follow these instructions to ensure that it starts up during boot time | ||
| + | * http:// | ||
| + | * Everything should now be in place and you can reboot the device and see if it is listed under **Accel-ppp Servers -> New Arrivals** | ||
| + | |||
| + | ==== RADIUS Client ==== | ||
| + | * If your Accel-ppp server is using RADIUSdesk for its RADIUS component you have one last step to do. | ||
| + | * You can do its RADIUS on-boarding by looking for it under RADIUS -> RADIUS Clients -> New Arrivals. | ||
| + | * After you completed the on-boarding be sure to specify the Client Type as **Accel-On-RADIUSdesk**. | ||
| + | * This will allow the code to follow the correct procedure when an active session for a user needs to be terminated. | ||
| + | {{: | ||
| + | |||
| + | |||