First of all we need to configure the RADIUS server on the router to communicate with Splynx.
In this case 10.250.32.1 is the Splynx server IP and 10.250.32.2 is the router IP. The RADIUS secret should be specified in the
Secret field - we will use this in Splynx in the router settings and then enable the
Lastly we need to enable
We can setup the DHCP server manually or using the setup wizard.
The main options here are:
Address pool=static-only (it means that Splynx (Radius server) will assign the IP) and
use RADIUS=yes. Specify the name, correct interface, lease time and save the settings.
Now we need to add a new router in Splynx under Networking → Routers → Add :
The main parameters here are:
IP / Host - IP of the router;
Authorization / Accounting - PPP/DHCP (Radius) / Radius acounting;
Radius secret - the same as the RADIUS secret on the router;
NAS IP - IP of the router.
In case you will use static IPs in Splynx you need to navigate to Networking → IPv4 Networks → Add and add a network with
Type of usage = static:
In this case we need to create IPv4 network with
Type of usage = Pool:
Under Customers → List select the customer, open Services tab and add a new internet service with following networking parameters:
IPv4 assignment method = Permanent IP(from static IPs), select the IP address and specify the MAC address of the interface on the CPE that will be receiving the IP.
Once this done the client should be connected:
On the router under the Leases tab we can see the DHCP lease with the IP that we specified in Splynx.
In Splynx we can see the customer's online session:
We can add more MAC addresses to the service field MAC(s) separated by a comma:
So a customer connection with the second MAC address can be authenticated:
Blocking of static IP customers will be performed using their own static IP in the address list. More information about customer blocking here - Blocking of customers in Splynx
Under Customers → List select the customer, open Services tab and add a new internet service with the following networking parameters:
and this connection will receive an IP from the specified pool:
Blocking of customers will be performed with reject IP pools in the address list. You can find more information about customer blocking here: Blocking of customers in Splynx.
For DHCP to report accounting correctly queues have to be applied dynamically via radius. API queues will not report the accounting stats to Splynx.
If you set additional network(s) in Splynx internet services, network routes will be sent to the router (NAS) during authorization. The router will then send all traffic with destination=additional network to the customer device. It is possible that these routes will also appear on the customer's device. To fix this issue, set use-framed-as-classless to disabled in the DHCP server settings:
What if the plan change queue was not updated and customer still has the same speed as on a previous plan? The reason is because CoA (change of authorization) and (Packet of Disconnect) is not supported by Mikrotik. The alternative is to use a short lease time which caters for any CoA related changes and "Disabled customers to address list" from API to block the customer's internet access.
To change the timeout, navigate to Config → Networking → Radius, find NAS config section, in NAS Type choose
MikroTik and press Load button. In the appeared MikroTik Configuration section, the following line should be added in the rate-limit-attributes (Access-accept) section:
Session-Timeout = "Lease time in seconds"
This config is critical and if not added the router will control the lease time internally, not release the IP and not renew the lease with the Radius server.
This is especially important when dealing with disabled services (disconnected without active service).
For more information, watch the next video: