In the 2.8 setup we have, new users are redirected to a series of pages that creates an account for them. Ultimately, they are then redirected to the page they wanted and authenticated based on the MAC address (sends MAC as username and password to Radius, upon http request?).
With 2.9, authenticate based on MAC sends MAC as username and blank password, so I made some changes to the accounts to accommodate. Works great for computers that already have an account. However, after a new user goes through the signup process, they don’t get authenticated based on MAC because they are already in the hosts table.
Is there a way to force the 2.9 Hotspot system to retry authentication based on MAC after they have created their account?
Under 2.8:
The login.html page has the option to create a new account or update an existing account. Both these links go to another box where we have some php and mysql stuff to update/create the accounts and handle billing. Once they have done with that the external page redirects to the original link.
At this point on 2.9, they still aren’t authenticated, so according to the Manual, redirect.html should redirect them to the login page.
If we put the above redirect in redirect.html or login.html, wouldn’t they originally get an endless cycle of trying to login by MAC and never get to the real login.html?