Hotspot login redirecting and HTTP post variables

RouterOS General
1

I’m updating an ancient hotspot (running 2.9.23) that redirects logins to an external HTTP server. It’s identifying itself and the user by including hidden post input in the redirect, i.e.:

	  
    <input type="hidden" name="mac" value="%mac%">
    <input type="hidden" name="hostname" value="%hostname%">

The router’s webserver then interpolates the variables and the identification is passed to the external server. Where can I find a reference to the interpolation and variables supported by the HTTP server on the router that serves the HTML stored on the router itself for RouterOS 4.x?

2

I don’t think it’s on the wiki yet, sadly, but the old documentation lists them all:

http://www.mikrotik.com/testdocs/ros/2.9/ip/hotspot.php

Look at the “Customizing HotSpot: HTTP Servlet Pages” section.

3

Yeah, I noticed that, but wasn’t sure if it was applicable to 4.x still. Will the HTML keep working properly after updating from 2.9 to 4.x?

In addition, the main reason I’m even considering this upgrade is because as far as I can tell 2.9 doesn’t support radius-location-name for hotspots. How would I include this in the redirect under 4.x (or 2.9 if I’m wrong about it not supporting radius-location-name?)

Alternately, is there any way to just include a hotspot-specific identification string in the radius request of a hotspot under 2.9? After rereading the 2.9 docs, it looks like I can just copy my redirect page to another directory and include a post request as a static entry in the HTML, as you can specify servlet HTML directories on a per-hotspot basis. However, I can’t find any way to authenticate the radius requests depending on which hotspot they come from.

4

I don’t know that you can pass that value on via a POST parameter in either. If you don’t receive other replies here maybe contact support@mikrotik.com for official support. If you do find out how to do this, please post it here.

Alternatively, set the Hotspot name (not exposed anywhere to the customer) to code for the RADIUS location as well. You can pass that on as described in the documentation.

5

After actually reading the 2.9 documentation in-depth, I may be able to identify the hotspot without doing any sort of software upgrade.

However, while it’s listed in the documentation as ‘WISPr-Location-ID - text string specified in radius-location-id property of the HotSpot server’, there doesn’t seem to actually be a radius-location-id property to set anywhere in the hotspot configuration, and none shows up on export of /hotspot. Is this just incorrect documentation or am I missing something?