I implemented a system like this some years ago, when user-manager was still beta. At the time, it wasn't going to be able to handle "Free" access.

What I did was implement a system whereby there was a linux based server on the network, running FreeRADIUS.

I created a PHP page on that server that the Mikrotik could link to for a signup form. In my case, I also captured and handed off the MAC address, but that may not be required for you to so do. In the Mikrotik login page the variable is $MAC.

From there, the user input the information I required which then simply inserted the rows into the FreeRADIUS database, then redirected the customer back to the Mikrotik login page. From there, they could log in with their newly created username & password.

Hi nickb,

so you use your custom php page as a walled garden?
I guess that every time that one user connect to the network, is redirected to your PHP page and made the registration to FreeRADIUS.

So why is needed RouterOS?

Hi nickb,

so you use your custom php page as a walled garden?
I guess that every time that one user connect to the network, is redirected to your PHP page and made the registration to FreeRADIUS.

So why is needed RouterOS?

The custom php page is only a signup form to allow users to create a username & password in the RADIUS server. ROS still handles all of the hotspot and access control.

I guess that every time that one user connect to the network, is redirected to your PHP page and made the registration to FreeRADIUS.

Is it correct?

I guess that every time that one user connect to the network, is redirected to your PHP page and made the registration to FreeRADIUS.

Is it correct?

No, the way I set it up is that the default Mikrotik hotspot login page is what they will see. There's simply a link on that page to the registration server.

Once registered, the user simply logs in with their username & password whenever they want to use the system.