User Manager is RADIUS server implementation in RouterOS which provides centralized user authentication and authorization to a certain service. Having a central user database allows better track of system users and customers. As a separate package, User Manager is available on all architectures including SMIPS, however care must be taken due to limited free space available. It supports many different authentication methods including PAP, CHAP, MS-CHAP, MS-CHAPv2, EAP-TLS, EAP-TTLS and EAP-PEAP. In RouterOS, DHCP, Dot1x, Hotspot, IPsec, PPP, Wireless are features that benefit from User Manager the most. Each user can see their account statistics and manage available profiles using WEB interface. Additionally, users are able buy their own data plans (profiles) using the most popular payment gateway - PayPal making it a great system for service providers. Customized reports can be generated to ease processing by billing department. User Manager works according to RADIUS standard defined in RFC2865 and RFC3579.
RADIUS attributes are defined authorization, information and configuration parameters that are passed between the RADIUS server and client. User Manager allows sending customized attributes defined in "attributes" menu. RouterOS has a set of predefined attributes already present, but it is also possible to add additional attributes if necessary. Predefined attributes:
|Attribute||Vendor ID||Type ID||Value type||Packet type||Description|
|0 (standard)||8||ip address||Access-Accept||RFC2865 section 5.8|
|0 (standard)||9||ip address||Access-Accept||RFC2865 section 5.9|
|0 (standard)||27||integer||Access-Accept, Access-Challenge||RFC2865 section 5.27|
|0 (standard)||28||integer||Access-Accept, Access-Challenge||RFC2865 section 5.28|
|Access-Accept||RFC2868 section 3.1|
|Access-Accept||RFC2868 section 3.2|
|0 (standard)||81||string||Access-Accept||RFC2868 section 3.6|
|0 (standard)||88||string||Access-Accept||RFC2869 section 5.18|
|Framed-IPv6-Prefix||0 (standard)||97||ipv6 prefix||Access-Accept||RFC3162 section 2.3|
|0 (standard)||100||string||Access-Accept||RFC3162 section 2.6|
|0 (standard)||123||ipv6 prefix||Access-Accept||RFC4818|
|Framed-IPv6-Address||0 (standard)||168||ip address||Access-Accept||RFC6911 section 3.1|
|Mikrotik-Recv-Limit||14988 (Mikrotik)||1||integer||Access-Accept||Total receive limit in bytes for the client.|
|Mikrotik-Xmit-Limit||14988 (Mikrotik)||2||integer||Access-Accept||Total transmit limit in bytes for the client.|
User's group for local users.
HotSpot profile for HotSpot users.
PPP profile for PPP users.
|Mikrotik-Wireless-Forward||14988 (Mikrotik)||4||integer||Access-Accept||Not forward the client's frames back to the wireless infrastructure if this attribute is set to "0" (wireless only).|
|Mikrotik-Wireless-Skip-Dot1x||14988 (Mikrotik)||5||integer||Access-Accept||Disable 802.1x authentication for the particular wireless client if set to non-zero value (wireless only).|
|Access-Accept||WEP encryption algorithm( wireless only).|
|Mikrotik-Wireless-Enc-Key||14988 (Mikrotik)||7||string||Access-Accept||WEP encryption key for the client (wireless only).|
|Mikrotik-Rate-Limit||14988 (Mikrotik)||8||string||Access-Accept||Datarate limitation for clients. Format is: rx-rate[/tx-rate] [rx-burst-rate[/tx-burst-rate] [rx-burst-threshold[/tx-burst-threshold] [rx-burst-time[/tx-burst-time] [priority] [rx-rate-min[/tx-rate-min]]]] from the point of view of the router (so "rx" is client upload, and "tx" is client download). All rates should be numbers with optional 'k' (1,000s) or 'M' (1,000,000s). If tx-rate is not specified, rx-rate is as tx-rate too. Same goes for tx-burst-rate and tx-burst-threshold and tx-burst-time. If both rx-burst-threshold and tx-burst-threshold are not specified (but burst-rate is specified), rx-rate and tx-rate is used as burst thresholds. If both rx-burst-time and tx-burst-time are not specified, 1s is used as default. Priority takes values 1..8, where 1 implies the highest priority, but 8 - the lowest. If rx-rate-min and tx-rate-min are not specified rx-rate and tx-rate values are used. The rx-rate-min and tx-rate-min values can not exceed rx-rate and tx-rate values.|
|Mikrotik-Realm||14988 (Mikrotik)||9||string||Access-Request||If it is set in /radius menu, it is included in every RADIUS request as Mikrotik-Realm attribute. If it is not set, the same value is sent as in MS-CHAP-Domain attribute (if MS-CHAP-Domain is missing, Realm is not included neither).|
|Mikrotik-Host-IP||14988 (Mikrotik)||10||ip address||Access-Request||IP address of HotSpot client before Universal Client translation (the original IP address of the client).|
|Mikrotik-Mark-Id||14988 (Mikrotik)||11||string||Access-Accept||Firewall mangle chain name (HotSpot only). The MikroTik RADIUS client upon receiving this attribute creates a dynamic firewall mangle rule with action=jump chain=hotspot and jump-target equal to the attribute value. Mangle chain name can have suffixes .in or .out, that will install rule only for incoming or outgoing traffic. Multiple Mark-id attributes can be provided, but only last ones for incoming and outgoing is used.|
|Mikrotik-Advertise-URL||14988 (Mikrotik)||12||string||Access-Accept||URL of the page with advertisements that should be displayed to clients. If this attribute is specified, advertisements are enabled automatically, including transparent proxy, even if they were explicitly disabled in the corresponding user profile. Multiple attribute instances may be send by RADIUS server to specify additional URLs which are chosen in round robin fashion.|
|Mikrotik-Advertise-Interval||14988 (Mikrotik)||13||integer||Access-Accept||Time interval between two adjacent advertisements. Multiple attribute instances may be send by RADIUS server to specify additional intervals. All interval values are treated as a list and are taken one-by-one for each successful advertisement. If end of list is reached, the last value is continued to be used.|
|Mikrotik-Recv-Limit-Gigawords||14988 (Mikrotik)||14||integer||Access-Accept||4G (2^32) bytes of total receive limit (bits 32..63, when bits 0..31 are delivered in Mikrotik-Recv-Limit).|
|Mikrotik-Xmit-Limit-Gigawords||14988 (Mikrotik)||15||integer||Access-Accept||4G (2^32) bytes of total transmit limit (bits 32..63, when bits 0..31 are delivered in Mikrotik-Recv-Limit).|
|Mikrotik-Delegated-IPv6-Pool||14988 (Mikrotik)||22||string||Access-Accept||IPv6 pool used for Prefix Delegation.|
|Mikrotik-Wireless-VLANID||14988 (Mikrotik)||26||integer||Access-Accept||VLAN ID for the client (Wireless only).|
|Access-Accept||VLAN ID type for the client (Wireless only).|
|Mikrotik-Switching-Filter||14988 (Mikrotik)||30||string||Access-Accept||Allows to create dynamic switch rules when authenticating clients with dot1x server.|
|name (string; Default: )||Name of the attribute.|
|packet-types (string; Default: access-accept)|
|type-id (integer:1..255; Default: )||Attribute identification number from the specific vendor's attribute database.|
|value-type (string; Default: )|
|vendor-id (integer; Default: 0)||IANA allocated specific enterprise identification number.|
All RADIUS related information is stored in a separate User Manager's database configurable under the "database" sub-menu. "Enabled" and "db-path" are the only parameters that are not stored in User Manager's database and are stored in main RouterOS configuration table meaning that these parameters will be affected by RouterOS configuration reset. The rest of the configuration, session and payment data is stored in a separate SQLite database on devices FLASH storage. When performing any actions with databases, it is advised to make backup before and after any activity.
|db-path (string; Default: )||Path to location where database files will be stored.|
|db-size||Current size of the database.|
|free-disk-space||Free space left on the disk where database is stored.|
|load (name)||Restore previously created backup file in .umb format.|
|migrate-legacy-db (database-path; overwrite)||Convert old User Manager (from RouterOS v6 or before) to new standard. It is possible to overwrite current database.|
|save (name; overwrite)||Save current state of the User Manager database.|
Limitations are used by Profiles and are linked together by Profile-Limitations. RADIUS accounting and Interim updates must be enabled to seamlessly switch between multiple limitations or disconnect active sessions when download-limit, upload-limit or uptime-limit is reached.
To disconnect already active sessions from User Manager, accept must be set to yes on RADIUS client side. If simultaneous session limits are not unlimited (shared-users) and it has reached maximal allowed number, then router will try to disconnect older user session firstly.
User-Manager attempts to disconnect active session, before new user will be accepted (when appropriate limit is set), that's why in such setups it is suggested to use 1s for /radius client timeout.
|comment (string; Default: )||Short description of the limitation.|
|download-limit (integer; Default: 0)||Total amount of traffic a user can download in Bytes.|
|name (string; Default: )||Unique name of the limitation.|
|rate-limit-burst-rx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-burst-threshold-rx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-burst-threshold-tx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-burst-time-rx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-burst-time-tx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-burst-tx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-min-rx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-min-tx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-priority ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-rx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|rate-limit-tx ()||Part of MT-Rate-Limit RADIUS attribute. Refer to Queues#SimpleQueue.|
|reset-counters-interval (hourly | daily | weekly | monthly | disabled); Default: disabled)||Interval from reset-counters-start-time when all associated user statistics are cleared.|
|reset-counters-start-time (datetime; Default: )||Static date and time value from which reset-counters-interval is calculated.|
|transfer-limit (integer; Default: 0)||Total amount of aggregated (download+uptime) traffic in Bytes.|
|upload-limit (integer; Default: 0)||Total amount of traffic a user can upload in Bytes.|
|uptime-limit (time; Default: 00:00:00)||Total amount of uptime a user can stay active.|
Information about all received payments are available in this section.
|currency (string)||The currency used in the transaction.|
|method (string)||Service used for the transaction (currently PayPal only).|
|price (decimal)||Amount paid by the user.|
|profile (profile)||Name of the profile the user purchased.|
|trans-end (datetime)||Date and time when the transaction started.|
|trans-start (datetime)||Date and time when the transaction ended.|
|trans-status (string)||Status of the transaction. Possible statuses - started, pending, approved, declined, error, timeout, aborted, user approved. Only approved should be considered as complete transaction.|
|user (string; Default: )||Name of the user who performed the transaction.|
|user-message (string; Default: )|
|comment (string; Default: )||Short description of the entry.|
|name (string; Default: )||Unique name of the profile.|
|name-for-users (string; Default: )||Name of the profile that will be shown for users on the Web page.|
|override-shared-users (decimal | off | unlimited; Default: off)||Whether to allow multiple sessions with the same user name. This overrides the shared-users setting.|
|price (decimal; Default: 0.00)|
|starts-when (assigned | first-auth; Default: assigned)||When does the profile become active. Assigned - immediately when a User Profile entry is created. First-auth - upon first authentication request from the user.|
|validity (time | unlimited; Default: unlimited)||Total amount of time a user can use this profile.|
Profile-Limitations table links Limitations and Profiles together and defines its validity period. When multiple Limitations are assigned to the same Profile, a user must comply with all Limitations for session to establish. This allows more complicated setups to be created, for example, separate monthly and daily bandwidth limits.
|comment (string; Default: )||Short description of the entry.|
|from-time (time; Default: 00:00:00)||Time of day when the limitation should start.|
|limitation (limitation; Default: )||Name of already created Limitation.|
|profile (profile; Default: )||Name of already created Profile.|
|till-time (time; Default: 23:59:59)||Time of day when the limitation should end.|
|weekdays (day of week; Default: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday)||Day of week when the limitation should be active.|
Here are defined all NAS devices that can use User Manager as RADIUS server.
|coa-port (integer:1..65535; Default: 3799)||Port number of CoA (Change of Authorization) communication.|
|address (IP/IPv6; Default: )||IP address of the RADIUS client.|
|comment (string; Default: )||Short description of the NAS.|
|disabled (yes | no; Default: no)||Controls whether the entry is currently active or not.|
|name (string; Default: )||Unique name of the RADIUS client.|
|shared-secret (string; Default: )||Used to secure communication between a RADIUS server and a RADIUS client.|
|reset-counters ()||Clear all statistics for specific RADIUS client.|
Sessions are logged only if accounting is enabled on NAS.
|acct-session-id (string)||Unique identification of the accounting session.|
|active (yes | no)||Whether the session is currently used.|
|calling-station-id (string)||User's identifier, usually IP address or MAC address.|
|download (Bytes)||Amount of traffic downloaded.|
|ended (datetime)||Date and time when the session was closed. Empty for active sessions.|
|last-accounting-packet (datetime)||Date and time when the last accounting update was received.|
|nas-ip-address (IP address)||IP address of the NAS.|
|nas-port-id (string)||Identifier of the NAS port that is authenticating the user.|
|nas-port-type (string)||The port type (physical or virtual) that is authenticating the user.|
|started (datetime)||Date and time when the session was established.|
|status (list of statuses)||Possible available statuses of a session: start - accounting message Start has been received, stop - accounting message Stop has been received, interim - Interim update has been received, close-acked - session is successfully closed, expired.|
|terminate-cause (string)||Reason why the session was closed.|
|upload (Bytes)||Amount of traffic uploaded.|
|uptime (time)||Total logged uptime on the session.|
|user (string)||Name of the user.|
|user-address (IP address)||IP address provided to the user.|
|accounting-port (integer; Default: 1813)||Port to listen for RADIUS accounting requests.|
|authentication-port (integer; Default: 1812)||Port to listen for RADIUS authentication requests.|
|certificate (certificate; Default: )||Certificate for use in EAP TLS type authentication methods.|
|enabled (yes | no; Default: no)||Whether the User Manager functionality is enabled.|
|use-profiles (yes | no; Default: no)||Whether to use Profiles and Limitations. When set to no, only User configuration is required to run User Manager.|
|paypal-allow (yes | no; Default: no)||Whether to enable PayPal functionality for User Manager.|
|paypal-currency (string; Default: USD)||The currency related to price setting in which users will be billed.|
|paypal-password (string; Default: )||Password of your PayPal API account.|
|paypal-signature (string; Default: )||Signature of your PayPal API account.|
|paypal-use-sandbox (yes | no; Default: no)||Whether to use PayPal's sandbox environment for testing purposes.|
|paypal-user (string; Default: )||Username of your PayPal API account.|
|web-private-password (string; Default: )||Password for accessing /um/PRIVATE/ section over HTTP.|
|web-private-username (string; Default: )||Username for accessing /um/PRIVATE/ section over HTTP.|
|attributes (array of attributes; Default: )||Custom set of Attributes with their values that will additionally be added to Access-Accept messages.|
|caller-id (string; Default: )||Allow user's authentication with a specific Calling-Station-Id value.|
|comment (string; Default: )||Short description of the user.|
|disabled (yes | no; Default: no)||Controls whether the user can be used or not.|
|group (group; Default: default)||Name of the Group the user is associated to.|
|name (string; Default: )||Username for session authentication.|
|otp-secret (string; Default: )||A one-time password token that is attached to the password.|
|password (string; Default: )||Password of the user for session authentication.|
|shared-users (integer | unlimited; Default: 1)||Total amount of sessions the user can simultaneously establish.|
|add-batch-users ()||The command can generate multiple user accounts based on various parameters.|
|generate-voucher ()||Generates a file based on voucher-template that can be presented to the end user.|
|monitor ()||Shows total statistics for a user. Stats include total-uptime, total-download, total-upload, active-sessions, actual-profile, attributes-details.|
/user-manager user group
User groups defines common characteristics of multiple users such as allowed authentication methods and RADIUS attributes. There are two groups already present in User Manager called default and default-anonymous.
|attributes (array of attributes; Default: )||Custom set of Attributes with their values that will additionally be added to Access-Accept messages for users in this group.|
|comment (string; Default: )||Short description of the group.|
|inner-auths (list of auths; Default: )||List of allowed authentication methods for tunneled (outer) authentication methods. Supported inner authentication methods - ttls-pap, ttls-chap, ttls-mschap1, ttls-mschap2, peap-mschap2.|
|name (string; Default: )||Unique name of the group.|
|outer-auths (list of auths; Default: )||List of allowed authentication methods. Supported outer authentication methods - pap, chap, mschap1, mschap2, eap-tls, eap-ttls, eap-peap, eap-mschap2.|
This menu assigns users with a profile and tracks the status of the profile. A single user can have multiple profiles assigned, however only one can be used at the same time. A user will seamlessly be switched to the next profile when currently active profile expires without dropping the user's session.
|profile (profile; Default: )||Name of the profile to assign for user.|
|user (user; Default: )||Name of the user to use particular profile.|
|end-time (datetime)||Date and time the User Profile will expire.|
|state (running active | running | used)||Current state of the User Profile. Running active - currently used profile by the user. Running - a profile is ready to be used. Used - expired profile that can no longer be activated.|
|activate-user-profile ()||Make a User Profile entry active immediately.|
Customizable file reference
|css/login.css||Cascading style sheet file used in login prompt page.|
|css/user.css||Cascading style sheet file used in user's profile page.|
|img/PayPal_mark_37x23.gif||PayPal logo image.|
|img/ajax-loader.gif||Loading gif while processing page switching.|
|img/mikrotik_logo.png||MikroTik logo displayed on all pages.|
|user/login_dynamic.html||Layout of the login prompt page.|
|user/user_dynamic.html||Layout of the user's profile page.|
It is possible to create multiple new users with randomly generated username and password. For example, the following command will generate 3 new users with 6 lowercase symbols as the username and 6 lowercase, uppercase and numbers as the password.
The command generated users can be seen by printing the user's table:
It is possible to send additional RADIUS attributes during authentication process to provide NAS with custom information about the session, such as what IP address should be assigned to the supplicant or what address pool to use for address assigning.
To assign end user a static IP address, Framed-IP-Address attribute can be used. When using static IP address allocation, shared-sessions must be set to 1 to prevent cases when a user has multiple simultaneous sessions, but there is only one IP address. For example:
We can group up multiple similar users and assign RADIUS attributes to all of them at once. First of all, create a new group:
Next step is to assign a user to the group:
In this case an IP address from pool1 will be assigned to the user upon authentication - make sure pool1 is created on NAS device.
User Manager supports time based authentication token addition to user's password field that is regenerated every 30 seconds.
OTP depends on clock, so make sure time settings are configured correctly.
TOTP works by having a shared secret on the supplicant (client) and the authentication server (User Manager). To configure TOTP on RouterOS, simply set the otp-secret for the user. For example:
To calculate TOTP token on supplicant side, many widely available applications can be used, for example, Google Authenticator or https://totp.app/. Adding mysecret to TOTP token generator will provide a new unique 6 digit code that must be added to the users password.
The following example will accept user's authentication with calculated TOTP token added to the common password until a new TOTP token is generated, for example,
To generate a single user's printable voucher card, simply use the generate-voucher command. Specify the RouterOS ID number of the user or use find command to specify a username. A template is already included in User Manager's installation available in Files section of your device. You can customize the template for your needs.
The generated voucher card is available by accessing the router using a WEB browser and navigating to /um/PRIVATE/GENERATED/vouchers/gen_printable_vouchers.html
By default the printable card looks like this:
To access the PRIVATE path of the /um/ directory by the WEB browser, private-username and private-password must be configured. See Settings section.
It is possible to use different variables when generating vouchers. Currently, supported variables are:
$(username) - Represents User Manager username
$(password) - Password of the username
$(userprofname) - Profile that is active for the particular user
$(userprofendtime) - Profile validity end time if specified
It is possible to generate a CSV or XML file with multiple or all user credentials at once by using the export.xml or export.csv as voucher-template.
The command generates an XML file um5files/PRIVATE/GENERATED/vouchers/gen_export.xml which can either be accessible by WEB browser or any other file access tools.
In cases where a presentable network usage information is required by companies billing or legal team an automated session export can be created using generate-report command. The command requires an input of report template - an example of the template is available in um5files/PRIVATE/TEMPLATES/reports/report_default.html. Example of the report generation:
The generated report is available by accessing the router using a WEB browser and navigating to /um/PRIVATE/GENERATED/reports/gen_report_default.html
After logging into user's private profile by accessing the router's /um/ directory using WEB browser, for example, http://example.com/um/, he will be able to see all available Profiles in the respective menu. Profiles that have specified price value will have Buy this Profile button available.
After pressing the Buy this Profile button, the user will be asked to choose from available transaction service providers (currently only PayPal available) and later redirected to PayPal's payment processing page.
When the payment is completed, the User Manager will ask PayPal to approve the transaction. After approval, the profile is assigned to the user and is ready to use.
User Manager configuration
Start off by enabling User Manager functionality.
Allow receiving RADIUS requests from the localhost (the router itself).
Next, add users and their credentials that clients will use to authenticate to the server.
Configuring RADIUS client
For the router to use RADIUS server for user authentication, it is required to add a new RADIUS client that has the same shared secret that we already configured on User Manager.
L2TP/IPsec server configuration
Configure the IP pool from which IP addresses will be assigned to the users and assign it to the PPP Profile.
Enable the use of RADIUS for PPP authentication.
Enable L2TP server with IPsec encryption.
That is it. Your router is now ready to accept L2TP/IPsec connections and authenticate them to the internal User Manager.