Feature request/poll -> /ip/hotspot/active

RouterOS General
1

I will add my support to the following feature:

  • Add user manually in /ip/hotspot/active
  • Remember active users across reboots/reset of hotspot
  • Sync active user data sessions/states to backup server, redundancy is important!
  • All of the above suggested features
  • I do not use Hotspot
  • Don’t change anyting
0 voters

Hi

We have recently deployed a big MT hotspot solution. The customers are coming from DSL, optical and radio. They are behind their own NAT-router. I will issue a poll here, to see if i have community support that my feature request is valid, and useful. Vote in the poll, if you agree with one, or all of the functions requested.

Also, if you know oher hotspot systems who do this, please add them in a post. MT told me they would like to know of systems doing this. I only know of Coova and NoCat that does this.

Issue:

The main problem with hotspot is on the user side, where you have the following issues:

Browser will not follow redirect.
Customer is not able to input user/pass correctly (user error, but still)
Headless systems, where no browser interaction is possible… (VOIP directly on a public ip fx)
Cookie is only available on one unit. Will of course fail if a different unit tries to go online, and the username has logged off.

Also, there is no possibility to sync between a redundant hotspot, so if a failure occurs, all customers will have to relogin.

I have (by email) proposed the following for Mikrotik:

#1: Manually activate a customer from the hotspot. ( /ip/hotspot/active add user=john pass=1234 ip=1.1.1.1 mac=00:00:00:00:00:00 (optional) active=yes AAA=yes ) (Auth goes to local or remote authenticator)

#2: Remember all sessions/states across reboots/resets, so we dont get login-storm, and annoyed customers as well.

#3: Sync between redundant servers, altough, #1 makes this possible by script.

Thank you

__
Kim

2

What about options like “I don’t use hostpot” and “Leave it as it is” to also see how relevant the request globally is?
Remember, his would require diverting development sources on this topic and would be detrimental to other issues and features.

3

Those who don’t use or don’t want changes, won’t vote. So, the results, if any, will still reflect on how many wants it.

I dont think these features would require big resources and energy, everything is already in place, it is just a matter of allowing to edit the underlying user database manually and/or input credentials via different path than usual.

–

Kim

4

You may be right on this. But there are those that don’t vote because they don’t bother to, which mean they are indifferent, 50/50, whatever.
It may be more realistic and in the requests favor to allow a negative vote and report to those.
25% of voters sounds better than 0.01% of all users :sunglasses:

5

Changed it, but i lost all votes, all three of them.. thats on me, i should have figured…

–

Kim

6

I am happy to inform that #1 is implemented, and will be available in v6.34rc8 which will be available in short time :slight_smile:
With some scripting, #2 and #3 is fully available :smiley:

Syntax will be:

/ip hotspot active login user=test password=test mac-address=E8:50:8B:1C:95:7D ip=172.16.20.19

For device to get logged in it just needs to be detected in host table and the user that you want to use must be in user list or AAA server.

I deeply appreciate this, it will make the whole difference for me and my colleagues!

Thank you Krisjanis, developer who added it, and MikroTik in general :slight_smile:

\

Kim