I seem to be getting somewhere with it but its still not right.
Ive set the login.html on the local hotspot to the following:
...
$(if chap-id)
JavaScript required. Enable JavaScript to continue.
$(endif)
If you are not redirected in a few seconds, click 'continue' below
\
\
\
Ive also got my rlogin.html set to the following:
\
\
\
\
Login
body {
background-color: #222222;
}
\
\
I have file.php on my web server running fine with permissions 755 and chown to the web server user as per all other vhosts. md5.js is also there and similarly permissioned. Its all browsable from a normal PC and its also being called when I try to go through the hotspot without logging in. file.php is as follows:
<?php
$mac=$_POST['mac'];
$ip=$_POST['ip'];
$username=$_POST['username'];
$linklogin=$_POST['link-login'];
$linkorig=$_POST['link-orig'];
$error=$_POST['error'];
$chapid=$_POST['chap-id'];
$chapchallenge=$_POST['chap-challenge'];
$linkloginonly=$_POST['link-login-only'];
$linkorigesc=$_POST['link-orig-esc'];
$macesc=$_POST['mac-esc'];
?>
mikrotik hotspot > login
body {color: #ff7373; font-size: 10px; font-family: verdana;}
\
\
I put in my details for a user I have set up on the hotspot user manager but it then seems to go nowhere.
Looking through file.php on the server it seems to call for function doLogin() when post is happening but from there I cant really work out whats happening and its definitely not going any further.
Yea I had to work through that earlier but I got there with the walled garden.
Ive actually managed to work this out. My problem was essentially that I had rlogin,html sitting in the same directory as login.html and it was superseding and redirecting (as its supposed to do). That was skewing my results as I tested because rlogin was also pointing to my test server.
Eventually when I tried a new target file I realised that rlogin was keeping things pointed at the original and rlogin was not passing any of the variables up to the server.
So I took it back to basics and got logintest working again. And once Id done that and moved rlogin out of harms way it all clicked into place.
thanks for your suggestion though.
on to the next challenge. sorting out MAC authentication.