Im looking to create a hotspot/captive portal that will allow users to access wifi by logging in using social media or completing a small form. Returning customers will be automatically logged in (via MAC address I’m assuming). Authentication/accounting will be via an external radius server.
In my test lab I’ve setup freeRadius & daloradius and successfully created a hotspot on the mikrotik and hooked up to the external radius server. So all very straightforward when using the hotspot pages on the mikrotik.
Ideally my login pages will need to be hosted externally to incorporate social media logins, data capture and scalability more efficiently. Where I’m having trouble grasping the concepts are, when I redirect my hotspot users to an external login page how and where the radius authentication takes place to allow the user access to the wifi.
I envisage my external portal login page will receive variables from the mikrotik such as “host=$(server-name)&client_mac=$(mac)&client_ip=$(ip)&userurl=$(link-orig)&login_url=$(link-login-only)&error=$(error)&user=$(username)” but its then how this data is sent to the radius server for authentication and then how the mikrotik receives the response and allows access.
Grateful for any steers in the right direction!
Neil