User Manager/Hotspot Example
Bold text== Introduction == To make this setup, you should have running Hotspot server on the router. Let us consider configuration steps for HotSpot and User Manager routers, in order to use User Manager for HotSpot users.
HotSpot configuration
- Set HotSpot to use User Manager for HotSpot server users,
/ ip hotspot profile set hsprof1 use-radius=yes
- Add radius client to consult User Manager for HotSpot service.
/ radius add service=hotspot address=y.y.y.y secret=123456
‘secret’ is equal to User Manager router secret. ‘y.y.y.y’ is the User Manager router address. By default this is 127.0.0.1. If using a remotely located Router (perhaps via a VPN) then the IP address entered is the IP address of that remote Router. The router could be a Radius Server, or another ROS with User Manager installed.
- Note, first local HotSpot Users database is consulted, then User Manager database.
It means that if you have configuration in ‘/ ip hotspot user print’, users will be able to authenticate in HotSpot using this locally held data.
Delete users configuration from ‘/ ip hotspot print’ to stop using local HotSpot User database for authentication. To move batch of local HotSpot users to the User Manager database use export and import . Use text editor program to create appropriate file to import local users to the User Manager database.
If you have multiple Radius entries, then connections are attempted from top to bottom and the first Radius Server that responds (with ANY response, authenticated or not) aborts any further radius lookups. Therefore this is intended for the Hotspot to try to obtain a connection to a working Radius Server usually with the same identical database contents, e.g. a main server and an identical backup. Adding multiple entries is not intended for the scenario of using different Radius Servers where you wish the Radius Client to attempt to obtain authentication for a user login from multiple and completely different databases, trying each one in turn, obtaining failures to authenticate on each (wrong) one until eventually one obtains a valid authenticated response from the one single database that does contain their Radius record.
User Manager configuration
- First, you need to download and install User Manager package;
- Create User Manager subscriber (root customer). Note that when using a version 3.0 or newer, a subscriber called ‘admin’ is created automatically – you can skip the following stage and change ‘MikroTik’ to ‘admin’ in subsequent steps;
/ tool user-manager customer add login="MikroTik" password="qwerty" permissions=owner
- Add HotSpot router information to router list,
/ tool user-manager router add subscriber=MikroTik ip-address=x.x.x.x shared-secret=123456
‘x.x.x.x’ is the address of the HotSpot router, ‘shared-secret’ should match on both User Manager and HotSpot routers. Adding ‘x.x.x.x’ as a router allows Radius requests from ‘x.x.x.x’ to be passed to the Radius Server built into User Manager. Therefore if you have any remote ROS Hotspots that require access to this Radius Server, then all their IP addresses must be added to this list.
- Add HotSpot user information, it is equal to ’ip hotspot user’ when local HotSpot is used for clients
In version 3:
/ tool user-manager user add name=demo password=demo subscriber=MikroTik
In version 4:
/ tool user-manager user add name=demo password=demo customer=MikroTik
We discuss only basic configuration example, detailed information about ‘user’ menu configuration.
- You can use User Manager web interface after first subscriber created.
- To make sure, that client is using User Manager for AAA,
/ ip hotspot active print Flags: R - radius, B - blocked # USER ADDRESS UPTIME SESSION-TIME-LEFT IDLE-TIMEOUT 0 R 00:01:29:2... 192.168.100.2 1m29s
‘R’ means that client uses User Manager server for AAA services.
Video: https://youtu.be/Geid7ugU_Cs