What do I need?
In order to use a MikroTik device with the Network Check-In system on your Nexudus Spaces account you will need to get a MikroTik device running RouterOS 6.2 or newer. Most likely than not, you will need a "level 6" license for the device. Most resellers will provide the hardware and the license in a single package and pre-installed as with any other router in the market, all you need is to make sure you are getting the right license level.
How do I install it?
All RouterOS routers can be configured using a web portal like many other routers. If you are in a Windows machine, MikroTik provides a configuration tool (Winbox) which is way faster than accessing the web interface to change any configuration. All the steps in this guide are performed using Winbox. You can get this tool from here http://www.mikrotik.com/download.
These changes won't stop any of the other MikroTik features from working.
is guide won’t cover the basics of how to install a router. Normally the port #1 in a Mikrotik Router will be connected to your internet provider cable, while the rest of the ports will serve your internal network. Once you router is installed and you have internet access from your internal network you can then follow this guide.This is a basic an general diagram of how a Mikrotik device may be placed in your existing network.
Hotspot is how MikroTik routers call the authentication portals which will control access to the internet. You may have heard this also referred to as a “Captive Portal”.
You will need a hotspot with some modified HTML pages allowing to relay the authentication to our servers, as this is where all the check-in and member information will be. The Hotspot configuration for Authentication should be HTTP-CHAP and MAC. Make sure you choose "MAC as Username" in the Mac Auth Mode.
The Mikrotik hotspot requires only one user. You will need to enter these details on your Nexudus Spaces settings page here: https://spaces.nexudus.com/Settings#&tab-Integrations. The user's profile needs to allow shared users. We normally set it up to 1000 and used admin as the shared user.
Important: You *must* use the default profile for this. Do not create a new user profile.
Download the HTML pages from the same link (https://spaces.nexudus.com/Settings#&tab-Integrations) and create a new hotspot folder for your router named "nexudus". You can do this using the "Files" feature in WinBox.
Important: after creating the hotspot folder, copy all the files from the default folder to this new folder. Then replace the 3 files in that folder with the ones you downloaded from your Nexudus Spaces account. The best way to do this may be to drag the default folder to your local computer and then drag them back to the new folder.
Those files already have all the required configurations from your account settings, so you only need to move them to the right folder and copy the scripts as we explain below.
Lastly, you need to create some Walled garden IP entries so members can actually browse your site. In case they need to buy access to the space, manage their account and login.
xxxx.spaces.nexudus.com: replace xxx with the subdomain for your account
When hitting the hotspot, users are automatically redirected to us, so they will see something like this:
Unless we know who they are based on their mac address, in which case they see something like this:
In any case there is a link to register and to buy access time if you happen to have those options enabled herehttps://spaces.nexudus.com/Settings and products to sell time passes created herehttps://spaces.nexudus.com/Billing/Products.
Next you will need to use the scripts provided in the zip file. Paste the content of the scripts in the default user profile, making sure you use file "OnLogin_Script.txt" for the "On Login" script and the "OnLogout_Script.txt" file for the "On Logout" script.
Edit the hotspot profile and make sure MAC login as well as HTTP CHAP are enabled
Next, create a third script called "CheckActiveUsers" and use the content of the file "CheckActiveUsers_Script.txt" as the Source of that script. Make sure the script has, at least, the "write", "read" and "test" policies enabled.
Lastly, create a new schedule (System > Scheduler) to invoke this script every 15 minutes.