- #Mikrotik hotspot session logout how to#
- #Mikrotik hotspot session logout zip file#
- #Mikrotik hotspot session logout zip#
And the rules from Hotspot should be placed at the very bottom of the list, for this, in the user profiles in the Queue tab, put Insert Queue Before = bottom. In general, as I expected, no one bothers to clone the Simple Queue rule, automatically created by the hotspot service, with the new necessary values on a specific ip and put it at the top of the list and edit it with scripts if necessary.
#Mikrotik hotspot session logout how to#
Please log on to use the hotspot service.įree trial available, ?dst=&username=T-">click here.ĭ = ĭ = hexMD5('' + + '') Īt the top of this script is inserted with the php scripts, this script will collect the data variable hotspot that will be sent by, I found a relatively simple solution to how to control the speed of the user hotspot on the fly, without the need for a falloff. The script Login.php on live server / hosting server Input data variables that I used is the same for alogin.html, status.html, and logout.html, it’s no problem because this is the hidden varibles. So the data variables will be send with type “hidden” to the external url which is the login page of the external interface. Login.html no longer used for displaying the data hotspot variable, but only send/insert the data variables hotspot that will be redirected to the form of the external login.php If you are not redirected in a few seconds, click 'continue' below The script Login.html on the hotspot router files The client will send the input variables and see the data variables of the internal hotspot server through external hotspot pages or interface on live server. Actually It is the proses to access the internal hotspot server that will be redirected to the external pages on live server including the variables hotspot that used. So that in the hotspot directory on live server will looked like the picture below!Įxternal hotspot web interface on live server can work by the scripts itself or just from live server.
#Mikrotik hotspot session logout zip#
After the extraction successfully, we can remove the zip file. As usual go the file manager and find the hotspot directory on public_html of the hosting files and then you can extract the zip file. To extract the zip file, I must go to the cpanel and login with the account hosting.
#Mikrotik hotspot session logout zip file#
We are now on live server files, then extract the zip file on the hotspot folder. Create a new folder inside the hosting files or your website files just named with “hotspot”, and drag the zip hotspot file into the folder to upload the zip file. Login with your website files or hosting files with your account to the fireFTP and you can access and manage the hosting files on live server. Next, open the FTP application in this case I am using the add-on Mozilla Firefox, that is fireFTP. I think would be nice if we collect md5.js to the js folder, so outside of folder we just only have the main html of the hotspot files by removing the others html file that we do not require.Ĭhange the html extension files (.html) to the php extension files (.php), then you can create the zip file from those files including the folder, so that it can be uploaded faster using FTP connection. That is css, img, fonts and js folder that containing the related file links. of course included with the file links that related to those files. Take Internal hotspot interface on your router to the folder of your local computer, we only use such as login.html, alogin.html, status.html, and logout.html. And the client see the login form again on login.php page. then login.html will be redirecting to login.php. Client request re logout : request will be sent to login.html.Client request logout : web interface pages will be sent the request to logout the client, status.html will be process it then will be redirecting and send the last statistic data variables to logout.php, then the client now in logout state on logout.php page.And status.html will be sent the statistic data variables and redirect to the status.php to display statistic data variables of the client. Client request status : After successfully logged in, the client is on alogin.php then request the status.While data login variables is false, request will be redirected back to login.php with the warning “login is wrong”. Client enter the data login: data login variables will be sent back to login.html, if it is true the process go to alogin.html, then alogin.html will be redirected to alogin.php, and the client see the alogin.php page on live server.Client request to login : request will be sent to login.html router, login.html will be redirected to login.php live server.