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:

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.

IP address management

IP addresses are used in every corporate or ISP network. They‘re an essential component of the whole networking. There are several ways to manage IP address assignments. Many administrators, even in large companies, are still using Excel sheets due to a lack of smart IP address management tools. We recommend our engine for IP address management. This module is connected to the customer database in Splynx. When IP address or subnet is assigned to a customer for his access, the IPs will be assigned in the IP address management tab as well. The main advantage of this is avoiding IP conflicts, when several customers get the same IP or an IP with the wrong range. Also you can always have an overview of the current situation with subnets.

Our video and screenshots below show a few steps for making this feature work:


1. Create a root network – create a larger network and add subnetworks to it. The root network is marked with yellow color.




IP addresses inside the selected subnetwork are shown in the table:


2016-01-26 10.43.12 pm



2. You can  statically define what a certain IP address is used for in the tool itself. When you assign IP address to the customer, it’s locked in the IP address management tool, and if you try to assign an IP that is already in use, the system will prevent it.


2016-01-26 10.46.05 pm


3. As an extra feature you can send a Mass ping to devices in the selected network, split the network into smaller subnets or merge the network into large one. You can switch to a graphical map view with icons to get quick information. All red icons mean that the IP address is not responding on Mass ping.

2016-01-26 10.43.28 pm

You can find a detailed explanation of IP address management in our video tutorial:

You can customize colors and types of devices, as well as add new types of equipment. Screenshot shows an example of how to visualize small networks /29,/28 etc. in one common /24 network

IPAM customization

Second video tutorial shows, how to customize IP address management module, and add more colors to it:


Splynx monitoring and weathermaps

Splynx monitoring is based on SNMP, RRD and Ping toolsThe administrator can set up monitoring for any OID supported by hardware vendors and draw charts with Splynx. The statistics are linked to customers account that gives them a possibility to check the used data through the Portal or mobile app. 

Our monitoring supports weathermaps as it’s shown in the picture below. At the moment you can use open source projects and connect it to Splynx – It’s a very powerful tool for visual interpretation of networks and it can be easily connected to the Splynx ISP Framework.



Network monitoring enables the sending of alerts via email and sms gateways to be always aware of the status of your devices and take immediate actions.

The following pictures show SNMP logs and RRD charts. We are using RRD as a technology for data logging and generating charts.



SNMP monitoring is described in a video tutorial:

Example of setting up ping monitoring:

Example of Mikrotik CPU usage monitoring:


How to setup Mikrotik Memory usage monitoring: