Ubiquiti EdgeRouters pppoe Radius support

UBNT EdgeRouters can act as a PPPoE server, with authentication of CPEs, providing statistics, blocking end users, and setting up speed limits and FUP rules.

Let’s divide it into parts:

1. Configure EdgeRouter pppoe server with Radius
2. Configure EdgeRouter pppoe server for incoming radius packets
3. Add EdgeRouter to Splynx
4. Connect PPPoE customer and check that everything is working fine
5. Install other usefull tools to Edgerouter

1. Configure EdgeRouter Pppoe Server with Radius support

The first step is to upgrade the system to at least the 1.5 version and higher, because support of Radius attributes was added in this version to EdgeOS. The version we describe here is EdgeOS v1.8.5
Upgrade can be achieved in CLI with commands :
add system image http://dl.ubnt.com/...
add system image new-version-1085.tar

Second step – we need to define the IP address for communication between Radius and EdgeRouter.
In my case it’s, set it up as the main IP of EdgeRouter with a command (in configure mode):

set system ip override-hostname-ip

Then I setup the PPPoE server with mandatory settings:

edit service pppoe-server
set authentication mode radius
set authentication radius-server key 12345
set client-ip-pool start
set client-ip-pool stop
set interface eth2

Radius configuration can also be done in web browser:


2. Configure EdgeRouter PPPoE incoming packets

This is an important part because we need to change plans, disconnect customers or apply FUP rules. In all these cases Splynx Radius sends packets to Edge Router.
Default port is of UBNT is 3779. To enable incoming packet processing run these command on EdgeOS:

sudo cp /opt/vyatta/etc/pppoe-server/start-pppoe-radius-disconnect /config/scripts/post-config.d/

and reboot the router.

to debug, if packets are received use file pppoe-radius-disconnect.log:

tail /var/log/pppoe-radius-disconnect.log

example of output when packet disconnect was received by EdgeOS:


3. Add EdgeRouter to Splynx and set up settings in Splynx

Just add a router to Splynx in Networking -> Routers and choose the NAS Type Ubiquiti


You can add additional attributes to the configuration of NAS Type under Config -> Networking -> Radius.
By default we support radius-rate-limit attributes to setup speeds of PPPoE tunnels.

4. Connect PPPoE customer and check that everything is working fine

Now we can connect the PPPoE user to EdgeRouter and check that everything went fine.
With the „show pppoe-server“ command we can see how many users are connected to the PPPoE server.


In Splynx we can see whether a customer is online and get his stats.


When we click the disconnect button, the customer should dissapear from the online list and reconnect with a new session, which means that EdgeRouter accepted the incoming packet from Splynx Radius server.

5. Install other usefull tools to EdgeRouter

PPPoE client tunnels are dynamically created and are not shown in the web dashboard. We need to get statistics of customer throughput, and a simple way to do it is to install the software bwm-ng. It’s located in the Debian repository, which means we need to add new repositories first and then install bwm-ng.
Add new repositories :

set system package repository wheezy components 'main contrib non-free'
set system package repository wheezy distribution wheezy
set system package repository wheezy url http://http.us.debian.org/debian
set system package repository wheezy-security components main
set system package repository wheezy-security distribution wheezy/updates
set system package repository wheezy-security url http://security.debian.org

and install the tool

apt-get install bwm-ng

Now you can run bwm-ng -u bits to get the actual Kbps throughput of pppoe clients
Example of output of bwm-ng is in picture below:


Now you can configure Splynx Radius server with UBNT EdgeRouter and benefit from a fast router that delivers 1 million packets per second routing performance in a compact and affordable unit!

If you face any difficulties, use our forum – https://splynx.com/forums/ or submit us a ticket – https://splynx.com/my-tickets/

Manage your whole network ! Radius server + MikroTik API in Splynx

The core of the Splynx ISP Framework covers two important areas of ISP network management – AAA and bandwidth management. Radius server is used for these technologies : PPPoE, IPoE, DHCP, Hotspot, Static IPs. Mikrotik API can be used for advanced bandwidth management.

1. AAA. 

Authentication, authorization and customer accounting in an ISP network. Splynx has its own stable and scalable Radius server which helps you manage connections, hotspots, redirections, blocking of non-payers and admin access to equipment. More information about AAA in Splynx can be found in the following article: https://splynx.com/3186/splynx-radius-server/

2. Speed limitation and queues. 

Mikrotik RouterOS has a smart system of Queue Trees which can be used for contention purposes, limitation of speed and time-based access.
When you have hundreds or thousands of customers, you should create and maintain many different rules – one rule per customer + setup parent Queues for contentions!  

You can manage all Mikrotik queues centrally from Splynx. You can also upload local authentication rules, such as DHCP bindings, PPPoE users, Firewall entries or Wireless Access List using Mikrotik API. Authentication can be combined with the Radius server. At the same time Splynx supports Radius and Mikrotik API.

We provide a way to divide where authentication is created and where queues are set up. This is used widely in Wireless ISP networks, because authentication is made in the AP closest to the customer, but queues are created in a central point or several central points. Another important feature is its ability to have same queuing rules on different routers in mirroring mode.

Let’s imagine a situation when we are authenticating users in each AP with Radius DHCP and creating queues in our main location via the Internet. But then, we get a second uplink in different location. There is an obvious need for queues in the second Uplink location too, because customers can be routed to both of these routers, it depends on the internal routing protocol. That is shown in the example below:


Splynx has a solution for setup with Mikrotik routers. As we described above, Splynx can authenticate users in one router, create queues in a second router and mirror them to a third router. This is achieved thanks to a flexible and stable API Framework internal infrastructure.

In the video manual below we describe advanced features and setup of MikroTik API and Radius in the Splynx ISP Framework.