1 Reply by jonallport

(4 replies, posted in Special Configurations)

I have exactly this setup for 2 customers.

(1 - A company with WiFi for visitors)
Just setup a generic username/password and edit hotspotlogin.??? so that the form has hidden fields for username/password which are pre-populated.
i.e. <input type="hidden" name="username" value="wifiuser"><input type="hidden" name="password" value="secretword">

The user will just then just see a button for 'login' - press to continue!


(2 - A hotel with Internet access in rooms / wifi in public areas)
Setup a generic username with a password of 'on', then edit hotspotlogin.??? as above so that the username field is pre-populated but for password:
<input type="checkbox" name="password">

The user will then see your splash/terms and conditions and can check the box to confirm their acceptance thereof.

Both of these methods work well and don't require any funny configuration other than editing the cgi login page (I use a PHP version but the idea is the same)

Go to forum: Special Configurations

2 Reply by jonallport

(9 replies, posted in Chillispot Configuration)

I have seen this problem where the chillispot is on a private (NAT'd) network and is NAT'ing (default);  The VPN/GRE packets are 'too' encapsulated !!!

GRE[NAT[GRE[NAT[PAYLOAD]]]] sort of thing, this second layer of NAT/GRE sticks a spanner in the works - is this the case for you?

Go to forum: Chillispot Configuration

3 Reply by jonallport

(8 replies, posted in Chillispot Configuration)

Nope, that didn't work; $userurl is empty for me!

Will have another look.

Go to forum: Chillispot Configuration

4 Reply by jonallport

(8 replies, posted in Chillispot Configuration)

Having just looked at your question again, and re-read hotspotlogin.??? examples I have to hand:

Try changing:

opener.location = \"about:home\";

to

opener.location = $userurl;

$userurl is a variable pulled from the original, intercepted page request.  and (hopefully) contains the URL that was intercepted to redirect to the landing page.  I'll try this myself and post feedback!

:^)

Go to forum: Chillispot Configuration

5 Reply by jonallport

(8 replies, posted in Chillispot Configuration)

It's quite easy to tune.

Edit /usr/lib/cgi-bin/hotspotlogin.cgi (or whatever you're using, for me it would be /var/www/hotspotlogin.php), look for

opener.location = \"about:home\";

and change about:home to whatever you want the post-auth location to be.  Don't forget to '\' any special characters (",/ etc).

Hope that helps

Jon
:^)

Go to forum: Chillispot Configuration

6 Reply by jonallport

(2 replies, posted in UAM Configuration)

What is unique and identifiable about these nodes?

(From a PHP perspective) there's plenty you can look at to discriminate: IP addresses, hostnames, machine architecture, browser version etc...

Is that of a any use?

Go to forum: UAM Configuration

7 Reply by jonallport

(3 replies, posted in Chillispot Configuration)

Hmm, methinks:

Setup the c/spot with mysql as per the HOWTOs, also there's a handy php version of hotspotlogin floating around, get that too.  Then the hard part.

I'd see if you could write the desired username/password to the mysql 'radius' table via the php hotspotlogin which the NAS will then read out.  That way you can stick anything in for username and password, it will be stored in mysql, and it will always authenticate OK.

Don't ask me about the details, I don't know nearly enough php to do it I'm afraid!

I hope that makes sense and seem feasible.

Jon

Go to forum: Chillispot Configuration