It is easy to add routers. There are mandatory fields to be filled when adding a router::

Name - router's identification in the system
Model - the type and manufacturer
Location - place where the router is connected
Address - physical address of the router
IP address - IP address of the router
Login (API) - MikroTik admin login for API access to the router
Password (API) - MikroTik API password
SNMP Monitoring - if yes, the MikroBill will download information over SNMP and monitor the situation and traffic on the router
SNMP community - password for communication over SNMP
Autorization / Statistics - type of customers' authorization, in this case static DHCP lease for each active user over MikroTik API.
NAT - enables or diables natting on the router

See following figure:

EN-add-router.png

To edit router details, click Networking at the top of the page and select Routers. Click Edit at the right side on the line assigned to the relevant router. Every value stands for a certain parameter of the router.

Information - general information about the router
API - if this is a MikroTik router, it is possible to manage it over the API interface
IP networks - defines routed networks, of which is possible to assign the IP addresses to customers
Speed limits - definition of maximum speeds for whole router and particular network cards
QoS - the Quality of Service and its settings, defines the priorities of particular services
Firewall - central management of MikroTik routers firewall rules
Status - router information received over the API
Log - general recording about MikroBill connections to the API

EN-edit-router.png

Guide for customer authentication (menu Authorization /Statistics):

No one / IP accounting - the users are not being authorized to the network. However, the Internet connection statistics are available anyway as MikroBill updates the database every 5 minutes over the API.

PPP (Radius) / Radius accounting - PPPoE or PPPtP user authentication using the Radius server.
DHCP (Radius) - DHCP user authentication using the Radius server (by user's MAC address). The Radius module has to be installed when using Radius option. It is not possible to get statistics over the Radius protocol when using DHCP Radius authentication, unlike the PPP. That is why MikroTik API is used instead

MikroBill loads local user authenication rules into the router, using the API. The statistics is being updated over the API and saved to MikroBill database every 5 minutes.
Firewall IP-MAC filter / IP accounting - is being used when user has a static IP address. The autentication in MikroTik router processes on the IP Firewall -> Filter rules level, see the following figure:

A-router-firewall.png

DHCP (Leases) - DHCP user autentication using a particular MAC address. The authentication itself processes on the IP DHCP Server -> Leases rules level, see the following figure:

A-router-dhcp.png

PPP (Secrets) - PPPoE or PPPtP local MikroTik router user autentication with no Radius server. The rules are being saved into the PPP -> Secrets. Note that it is necessary to set up server manually and to assign it to an interface, see the figure below:

A-router-ppp.png

Hotspot (Sessions) - Hotspot user authentication. The rules are being saved into the router, IP -> Hotspot -> Users:

A-router-hotspot.png

© 2013 MikroBill, all rights reserved