Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
technical:mikrotik-hotspot [2025/05/13 10:38] – [Prepare RADIUSdesk] system | technical:mikrotik-hotspot [2025/05/13 15:01] (current) – system | ||
---|---|---|---|
Line 11: | Line 11: | ||
With this scenario we assume you have: | With this scenario we assume you have: | ||
- | * A recent installation of RADIUSdesk | + | * A recent installation of RADIUSdesk. |
* We will use our **cloud.radiusdesk.com** demo server which has an IP Address of **164.160.89.129** in this document. | * We will use our **cloud.radiusdesk.com** demo server which has an IP Address of **164.160.89.129** in this document. | ||
* Our cloud.radiusdesk.com demo server has a site wide RADIUS shared secret of **testing123**. | * Our cloud.radiusdesk.com demo server has a site wide RADIUS shared secret of **testing123**. | ||
Line 154: | Line 154: | ||
Your Mikrotik Hotspot is now configured. Next we will prepare RADIUSdesk. | Your Mikrotik Hotspot is now configured. Next we will prepare RADIUSdesk. | ||
+ | |||
+ | ---------------- | ||
===== Prepare RADIUSdesk ===== | ===== Prepare RADIUSdesk ===== | ||
Line 164: | Line 166: | ||
* Ensure there is a unique identifier the RADIUS client can identify itself with to the server. (We did this by setting the Identity of the Mikrotik router.) | * Ensure there is a unique identifier the RADIUS client can identify itself with to the server. (We did this by setting the Identity of the Mikrotik router.) | ||
* After you took care of that simply reboot the Mikrotik router while it has an active Internet connection. | * After you took care of that simply reboot the Mikrotik router while it has an active Internet connection. | ||
- | * It should then be reported under the Unknown Clients list of the RADIUS → RADIUS | + | * It should then be reported under **New Arrivals - RADIUS**. |
- | * The Unknown Clients | + | * The **New Arrivals - RADIUS** |
- | * To launch it, click the Unknown Clients | + | * To launch it, click the **New Arrivals** |
- | ==== Converting An Unknown Client ==== | + | <panel type=" |
- | * After the Mikrotik appeared under the Unknown clients tab we can convert it to a known client. | + | {{: |
- | * Select the unknown client you want to convert and click on the Attach button. | + | </ |
- | * This will bring up a window where you can select the owner (if there are sub-providers belonging to the user who logged in) | + | |
- | * Next you can give it a name: | + | |
- | * The Monitor and Maps sub-tabs you can leave as default. | + | ---------- |
- | * The Enhancements tab has some handy enhancements. You are also advised to leave the defaults. | + | |
- | * Finally select some realms who you want to allow to use this RADIUS Client. If the list is empty, click on the Make available to sub-providers checkbox to give a list of realms belonging to sub-providers. | + | |
- | * After you click the Next button this item will be moved to the list of known Dynamic Radius Clients. As you can see this item indicates that it never contacted the RADIUSdesk server. | + | |
- | * Simply reboot the Mikrotik to confirm that contact is now established: | + | |
+ | ==== On-boarding a new arrival ==== | ||
+ | * After the Mikrotik appeared under the **New Arrivals - RADIUS** tab we can change it to a RADIUS Client. | ||
+ | <panel type=" | ||
+ | {{: | ||
+ | </ | ||
+ | * Select the new arrival you want to change and click on the **Attach** button. | ||
+ | * This will bring pop up a window where you can provide some detail. | ||
+ | * Give it a name: | ||
+ | <panel type=" | ||
+ | {{: | ||
+ | </ | ||
+ | * The **Monitor** and **Maps** sub-tabs you can leave as default. | ||
+ | * The Enhancements tab has some handy enhancements. You are also advised to enable auto close - We give it a value of one hour (3600 seconds) | ||
+ | <panel type=" | ||
+ | {{: | ||
+ | </ | ||
+ | * Finally select the realms that can use this RADIUS Client. | ||
+ | <panel type=" | ||
+ | {{: | ||
+ | </ | ||
+ | * After you click the **Next** button this item will be moved to the list of RADIUS Clients. You will see this item indicates that it never contacted the RADIUSdesk server. | ||
+ | * Simply reboot the Mikrotik to confirm that contact is now established. | ||
* This brings us to the end of this section. | * This brings us to the end of this section. | ||
+ | ----------- | ||
==== Testing it out ==== | ==== Testing it out ==== | ||
Line 192: | Line 211: | ||
* If things do not work correct; run a debug trace on FreeRADIUS and restart the Mikrotik router. | * If things do not work correct; run a debug trace on FreeRADIUS and restart the Mikrotik router. | ||
* Confirm that the Mikrotik router does send an Accounting-On packet to the RADIUS server by looking at the debug output of the FreeRADIUS server. | * Confirm that the Mikrotik router does send an Accounting-On packet to the RADIUS server by looking at the debug output of the FreeRADIUS server. | ||
+ | |||
+ | ------------- | ||
==== What next ==== | ==== What next ==== |