Understanding "Session History" "Connection History" states

[DenbyWireless]

I had one Mac client say he could not connect, just hung. Another Mac guy works fine. Go figure.
In my session history I found some states I did not understand and I was wondering if someone could explain the various states that are displayed in the session/connection history screen.

In my particular case, the following is returned with no duration. Ticket was for 30min, so this is close.
HornbyBikeShop anonymous t:RS-30m-0104 AUTH_OK  not started 2007-06-05 11:19:24   not stopped 
HornbyBikeShop anonymous t:RS-30m-0104 AUTH_OK  not started 2007-06-05 10:46:23   not stopped 

Here are the other states I've seen.

State
Auth_Failed
Auth_OK
STOP
STOP_NOT_RCVD

Under Terminate Cause
Session-Timeout (Monitored threshold exceeded Seems like either Volume or Time limit exceeded generate same terminate cause)
not stopped
Lost-Carrier
User-Request (normal clean exit by user)
  -and lets not forget
not stopped Hotspot needs credits or a subscription. Please contact hotspot owner about this. account limitations reached


Anyway thanks for your explanations

[WorldSpot]

In my particular case, the following is returned with no duration. Ticket was for 30min, so this is close.
HornbyBikeShop anonymous t:RS-30m-0104 AUTH_OK  not started 2007-06-05 11:19:24   not stopped
HornbyBikeShop anonymous t:RS-30m-0104 AUTH_OK  not started 2007-06-05 10:46:23   not stopped 

Auth_ok means the radius authentication request has been received and answered.
However, worldspot did not receive the radius accounting start request, probably because your hotspot did not receive the  radius auth response, probably because of an internet connectivity problem. Please try using US worldspot server.
Note: the coova autoconfig has been fixed for the US server.

Session-timeout: time limit reached
not stopped: Stop has not been received
Lost-Carrier: user closed wireless without loging out: auto logged out.

not stopped Hotspot needs credits or a subscription. Please contact hotspot owner about this. account limitations reached:
You didn't have enough credit for per ticket usage. the "Account limitation reached" message is a bug that has been corrected. Thanks for reporting.

[DenbyWireless]

So I just need to change the auto config from
https://secure2.worldspot.net.....
to
https://us.secure2.worldspot.net

Thanks

[WorldSpot]

No us.worldspot.net and secure2.worldspot.net go to the us server.

[DenbyWireless]

Trick here is to realize that you display the correct values when you connect to the US Servers.
Didnt realize that at first.  Thanks

[DenbyWireless]

I just had another support call on a Mac, in debugging w/another mac that works, I saw this WORKING MAC GENERATE THE FOLLOWING;
HornbyBikeShop anonymous t:DW-CM-0101 AUTH_OK  not started 2007-06-05 11:19:24   not stopped

This is on the US Servers.  This Mac IS working and surfing Google and MSN.  So I think there is more to this than just changing servers.

Funny how it shows a row for ended connection just 1/2 hour later.  Customer say's normal access for their 1/2 hr. (30min ticket)

HornbyBikeShop anonymous t:RS-30m-0104 AUTH_OK  not started 2007-06-08 12:32:05   not stopped
HornbyBikeShop anonymous t:RS-30m-0104 AUTH_OK  not started 2007-06-08 12:01:24   not stopped 


Any other ideas ?  This will affect your billing as these not started clients are not logged as connected.

Thanks

[WorldSpot]

I'm suspecting you are using the latest coova firmware, and it seems there is a big problem with it.
In my logs I can see that the accounting radius requests have a wrong radius secret. This is why you don't get start and stops.
Please tell me what version are you using and I will report this to coova author.

Note that I noticed no problem when I tested the latest coova chilli svn.
Please upgrade or downgrade to another coova chilli version by using the command

Code: [Select]

ipkg install http://ap.coova.org/tmp/coova-chilli-r64.ipk

[DenbyWireless]

Note that I noticed no problem when I tested the latest coova chilli svn.
Please upgrade or downgrade to another coova chilli version by using the command

Code: [Select]

ipkg install http://ap.coova.org/tmp/coova-chilli-r64.ipk

I did the upgrade last night, but here there morning I'm seeing the same thing for the same ticket.
Essentially this ticket has been used 3 times when it should have only been used once.
It's not a big deal,  but it is funny that this hotspot is having trouble when I'm not seeing this on the other.

Could something have been stored incorrectly in your DB, so this ticket will always be messed up?

[WorldSpot]

Exact, there is still a problem with your only one hotspot (around 18h30 gmt+2)
The accounting radius requests have a bad secret.

This is a problem with your configuration which may cause this bug.
Try to disable the "exotic" options you have.
You should see 'started' in your hotspot history. If you get auth_ok, this is NOT normal.
Is it the local mac authentication?

[DenbyWireless]

No exotic options used.  In fact both my hotspots are same hardware and version (or were before last update).

Another thing I've noticed is the fact that my Commuter tickets sold do not seem to be working on both sites.

See Ticket DW-CM-0108.  I just tried this in my BBstore site. This ticket is listed correctly as being valid in both spots.
Not sure why This is not working but it's a real problem for me.  I just tried this ticket, it says wrong ticket/pswd.
I just validated the user and pswd in ticket list.  Yes I'm choosing Ticket login and I'm following case.

Can you check your logs again. Prime time starts next week...Thanks.

[WorldSpot]

Looking at your hotspot history, things look clear.
HornbyBikeShop has a problem since 2007-06-05 10:46:23, and has not been corrected since.
All your other hotspots are fine.
Please upgrade to latest coova beta.5 or dd-wrt and test again to get rid of these auth_ok.
I don't think it is related to your ticket, but to your hotspot.
In my logs, I can see the problem which can't be related to the database, but your radius accounting secret is wrong, so it is ignored. What is very strange and let me think it is a bug, is that your radius authentication and your radius accounting have different secrets.

[DenbyWireless]

Looking at your hotspot history, things look clear.
HornbyBikeShop has a problem since 2007-06-05 10:46:23, and has not been corrected since.
All your other hotspots are fine.
Please upgrade to latest coova beta.5 or dd-wrt and test again to get rid of these auth_ok.
I don't think it is related to your ticket, but to your hotspot.
In my logs, I can see the problem which can't be related to the database, but your radius accounting secret is wrong, so it is ignored. What is very strange and let me think it is a bug, is that your radius authentication and your radius accounting have different secrets.

Only thing I can think of wast that I was unable to remote admin this site via the GUI.
So I used SSH to do the change from the UK to US Server.

All I did was to update the hs_radconf_url via nvram get, nvram set, nvram commit.
seetings are now hs_radconf_url=https://secure2.worldspot.net/wk/Coova?spot=HornbyBikeShop&secret=xxxxx

How off is the secrets ?  One letter at the end or completely different strings?

Can you think of any way I can perform the upgrade via the SSH window ?

Also, why would one of my commuter tickets that is supose to work at all my hotspots not work ?
(Seporate issue and unrelated ?)
Thanks

[WorldSpot]

Is this the one you upgraded to coova chilli r64?
Did you reboot with "reboot" after performing your upgrades?
I think it is possible to upgrade the firmware remotely with ssh.
Google around for this, this is documented in the openwrt wiki.

[DenbyWireless]

Is this the one you upgraded to coova chilli r64?
Did you reboot with "reboot" after performing your upgrades?
I think it is possible to upgrade the firmware remotely with ssh.
Google around for this, this is documented in the openwrt wiki.

Yes, at your request I upgraded.
One thing I rememered, when I set the hs_radconf_url, I had to put quotes around it.
nvram set hs_radconf_url="https://secure2.worldspot.net/wk/Coova?spot=HornbyBikeShop&secret=xxxxx"
It displays fine, I didnt' think I'd need the quotes, but it seem to have needed it.

As to reboot. at the SSH prompt I typed reboot, and yes it seem to have rebooted correctly.
(I can tell because the dyndns entry gets reset on reboot because my IP is running as a DMZ, and this pick local lan address, not WAN)

I'm sorry to ask, but I'm remote without a lot of bandwidth. Pointers to Wiki docs would be helpful.
Thanks

[WorldSpot]

from openwrt wiki:

3.5. via the OpenWrt commandline
Reflashing OpenWrt will overwrite the filesystem, erasing all previous applications and data. You are strongly urged to back up any changes you may have made to the system.


mtd -r write firmware.trx linux
For models low on memory, the firmware can be flashed directly from a web site.

wget http://www.somesite.com/firmware.trx -O - | mtd -e linux -r write - linux