1 Topic by maxxer

(0 replies, posted in Chillispot Configuration)

Hi.

I've set my chilli.conf to have
interval 60
to reread dns and reload config every minute. Normally this isn't a big problem, but in a couple of places this operation takes up to 6 or 7 seconds, and during this period ALL the traffic is interrupted!
So if a user is on a skype conversation or watching a video or whatever, every minute the connection is shut for a relevant amount of time.

And this is happening only at this place.

Using local dns cache cut down that time to the half, but still I have a 3s gap which I'm not experiencing on all the other installations.

Any idea what can cause this?
thanks

Go to forum: Chillispot Configuration

2 Reply by maxxer

(4 replies, posted in Chillispot Configuration)

What bug are you referring to? Chilli doesn't correctly apply upload limits?

Go to forum: Chillispot Configuration

3 Topic by maxxer

(0 replies, posted in Chillispot Configuration)

Hi.

I'm [still] using Chillispot, but I guess the problem could be unrelated to the client.
I'm experiencing problems with password encoding. I use GoLogin PHP login page, which works "mostly".

Now I have a very busy NAS which causes me troubles with a lot of failed logins. I invesigated long time on the radius server, but it seems that the problem is on the client side, since the password decoded by radius is wrong, as spotted in this debug line:

        User-Name = "MYUSERNAME"
        User-Password = "\002\234\350v[z\035Y\237\257\354\245\326\213\305."

I was obviously suggested that the secret is wrong, but I double checked and it's correct, in fact most (half?) of the logins are done correctly. Yet, many of them fail because the password is wrongly encoded.
How is it possible that the same login page generates a wrong password?

I tried configuring another nas with the same parameters, and logins are performed correctly, even with the credentials which just went wrong on the previous hotspot.

I don't know what could be wrong, any ideas?

Go to forum: Chillispot Configuration

4 Reply by maxxer

(2 replies, posted in UAM Configuration)

turned out to be a radio problem.
setting b-only and 11G solved the issue!
incredible...

Go to forum: UAM Configuration

5 Reply by maxxer

(2 replies, posted in UAM Configuration)

correcting myself, the issue seems to be related to wrt only.
chilli 1.0 on PC works hmm

Go to forum: UAM Configuration

6 Topic by maxxer

(2 replies, posted in UAM Configuration)

Hi.

I'm trying to let people access paypal even if not logged in.
I added www.paypal.com and www.paypalobjects.com to the uamallowed list, but the second site is not working properly.
I can access paypal.com without problems, but on paypalobjects.com I often get timeouts. It can rarely work, but 98% of the times goes timeout.

I tried bypassing chilli and everything works.
I'm on a WRT, but even on a PC with chilli does the same.

What could be the problem?
thanks

Go to forum: UAM Configuration

7 Reply by maxxer

(1 replies, posted in Radius Configuration)

no. both server & client 32bit

Go to forum: Radius Configuration

8 Topic by maxxer

(1 replies, posted in Radius Configuration)

Hi.

On an highly used HotSpot, I get a lot of error messages like these:

Jul  8 11:36:18 hotspot chillispot[2540]: chilli.c: 3082: New DHCP request from MAC=00-26-FF-76-xx-xx
Jul  8 11:36:18 hotspot chillispot[2540]: chilli.c: 3052: Client MAC=00-26-FF-76-xx-xx assigned IP 172.16.12.143
Jul  8 11:36:22 hotspot chillispot[2540]: radius.c: 235: No such id in radius queue: 12!
Jul  8 11:36:22 hotspot chillispot[2540]: radius.c: 1473: Matching request was not found in queue: 12!
Jul  8 11:36:22 hotspot chillispot[2540]: chilli.c: 3696: radius_ind() failed!
Jul  8 11:36:40 hotspot chillispot[2540]: radius.c: 235: No such id in radius queue: 15!
Jul  8 11:36:40 hotspot chillispot[2540]: radius.c: 1473: Matching request was not found in queue: 15!
Jul  8 11:36:40 hotspot chillispot[2540]: chilli.c: 3696: radius_ind() failed!

I have several HS installed, but this is the only one where I get such errors.
This is also the most heavily used one.

What can cause this?
thks

Go to forum: Radius Configuration

9 Topic by maxxer

(1 replies, posted in Chillispot Configuration)

Hi.

I often get such error messages on a chillispot installation. it's the first time, and i have several of them around.
this chilli is connected to internet using a long distance wifi connection, which can have some more latency than an usual dsl.

is there anything i can do to have chilli better fit the connection? users often run in failed logins!

thanks
maxxer

Go to forum: Chillispot Configuration

10 Reply by maxxer

(3 replies, posted in UAM Configuration)

thanks, but I would like to know it BEFORE login, in order to forbid. radacct is populated only after successful login

Go to forum: UAM Configuration

11 Topic by maxxer

(3 replies, posted in UAM Configuration)

Hi

Is there any way to know the MAC address of the chilli machine (being it a pc or a wrt) at login stage?
You already have chal, client mac, uamip, uamport, but I would also need to identify the NAS.
Is it possible?
thanks
maxxer

Go to forum: UAM Configuration

12 Reply by maxxer

(11 replies, posted in Chillispot Configuration)

in radius.conf, check that into the accounting and authorize sections you have commented the lines of radutmp and sradutmp (maybe only in accounting, can't remember exactly right now)

Go to forum: Chillispot Configuration

13 Reply by maxxer

(11 replies, posted in Chillispot Configuration)

cmos wrote:

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 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!

Go to forum: Chillispot Configuration

14 Reply by maxxer

(11 replies, posted in Chillispot Configuration)

ajauberg wrote:
$q="UPDATE radacct SET AcctStopTime=now(), AcctTerminateCause='Chillispot Restart' WHERE AcctStopTime ='0000-00-00 00:00:00'"; 
mysql_query($q) or die (mysql_error());

I am doing this but yet this doesn't re-enable users login! This just resets the table.
Often I need to radzap the user, but yet this doesn't clear the radacct entry.

My users all have Acct-Interim-Interval := 60 in the radgroupreply table and Idle-Timeout := 600, but after NAS restart in radwho and radacct table I see stale users for ages!

Go to forum: Chillispot Configuration

15 Topic by maxxer

(1 replies, posted in Chillispot Configuration)

Hi
I have problems with stale/pending sessions.

I have already activated the "clearing" of the radacct table when chilli starts, as stated in a previous thread.

From the previous forum I also learned that to reduce the this issue the Acct-Interim-Interval row had to be inserted in the reply table.

Sadly, all this isn't helping, because I still experience some pending users in certain circumstances. It seems that most of them happens when the chilli machine is restarted. At this time the radacct table is reset with the query, but the users still appears as online in radwho. Most of the time to allow their login again I need to radzap them, since I have Simultaneous-Use = 1 too.

What am i missing to have chilli close all the pending sessions on reboot?

thanks
maxxer

Go to forum: Chillispot Configuration