1 Reply by cmos

(11 replies, posted in Chillispot Configuration)

maxxer wrote:

i modified my radius configuration so that stores accounting and all other information ONLY on the db. This solved (i'm almost sure) all the problems of my stale sessions. so you store the users information on file OR on sql, but not both!

Thanks for the info maxxer. I've look in my radius.conf but can't really sure what to put and where. Could you point me to the right direction. BTW, I've check radwho file and with "radwho -ZRN 10.0.0.1 | radclient -f - radius.example.net acct testing123", one can zap all user connected to the NAS in one go. But, I rather not reinventing the wheel if you already have a working solution.

EDIT: nevermind. Found it. Thanks for the solution maxxer.

Thanks.

Go to forum: Chillispot Configuration

2 Reply by cmos

(11 replies, posted in Chillispot Configuration)

True as maxxer said that this will only clear the database table but the user who is online during chilli restart can't login due to stale session in radius if simultaneous-use attribute is set to 1. Due to that, this workaround didn't solve the problem totally. I'm not knowledgeable with scripting but I've an idea if somebody can help write it.

The idea is to clear the database table and execute radwho and radzap when chilli restart. The first problem is solved with the solution post by ajauberg. Now to the second step. Use radwho -r to get list of username that hanging in radius right after the restart happen and feed it to the radzap to delete it from radius. So, no more stale in database table and radius will also be clear from it and users with simultaneous-use = 1 can login again without "you are already login" error.

I suppose a knowledgeable person in scripting/perl can combine both radwho and radzap in one script because I believe that radzap itself use radwho and radclient. Maybe a little modification to radzap can make this happen. Later (I suppose), one can add the code in chilli.ipup.php to call the script and execute it.

Thanks.

Go to forum: Chillispot Configuration

3 Reply by cmos

(2 replies, posted in Chillispot Configuration)

comment out the https part in hotspotlogin.cgi

#If she did not use https tell her that it was wrong.
if (!($ENV{HTTPS} =~ /^on$/)) {
print "Content-type: text/html\n\n
<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\">
<html>
<head>
............
............
";
exit(0);
}

Go to forum: Chillispot Configuration

4 Reply by cmos

(11 replies, posted in Chillispot Configuration)

Hi ajauberg,

I guess this will not work if chillispot is in the router box (DD-WRT firmware) and everything else is in separated server? Sometime the chilli's daemon on the router restart out of nowhere and how can I make it exec the php script in the server from the router box?

Thanks.

Go to forum: Chillispot Configuration

5 Topic by cmos

(0 replies, posted in Chillispot Configuration)

Hi all,

I've googled the above and found that there's a patch which we can apply to chillispot to send customized message to user but it's in the old forum and I can't find it. Anyone know how to do this?

I'm using hotspotlogin.cgi + chillispot in DD-WRT + mysql + freeradius in debian. The message sent to user when their time end is "Your maximum never usage time has been reached" which sound inappropriate because of the word "never". I believe freeradius took that directly from Max-All-Session attribute where I set reset to "never".

Go to forum: Chillispot Configuration

6 Topic by cmos

(0 replies, posted in Chillispot Configuration)

Hi all,

I don't know which section to post this so I choose the most active. Pls move to another section if it's not appropriate.

Today a user can't login and complain that their one month account has reach the maximum usage which is not supposed to happen yet. So, I check the problem and found that 3 user has their AcctSessionTime in radacct table with a ridiculous value and way exceed 2592000 (30 days) which is not supposed to happen except if there is some glitch somewhere. I did solve it by removing the entries and restart the whole server. Removing the entry alone without restarting the sever did not fix it. They can login but time left is just 5 hours instead of 29 days.

I'm trying to figure out what had happened by checking some log in the server but found nothing. I'm afraid that this is a bug and might happen again and need to find the cause. So, could someone advice me where to look? What's the likely reason to this? 

Thanks.

Go to forum: Chillispot Configuration