Understanding "Session History" "Connection History" states

[DenbyWireless]

I have one hotspot site that has had problems logging activity. I’ve reported the problem to here, and so somehow some of my accounting packets are coming thru with the wrong secret.
I’ve traveled (by Ferry) to the hotspot, and I’m there now.  I’ve erased the nvram via the open-wrt clear script (nvram-clear.sh w/nvram commit) and re-flashed to B5, same accounting issues.
HornbyBikeShop anonymous t:DW-Test-0109AUTH_OK not started 2007-06-21 13:34:22 not stopped

Downgraded to B4, installed the ipkg install coova-chilli patch Same issue.

One thing of interest is that the Firmware upgrades does the write of .bin to linux, but never comes back. Router is up, and after a while if I start another window I can see that the router has been upgraded (or Downgraded) and asks for psde.
So I know the flash is taking but I wonder about the erase. I've waited 20min for it to 'finish'.

What kills me, is I have the EXACT setup at another site and it works flawlessly.

Any of this sound familiar ?  I'll PM my nvram show to you in a sec.
 
Even though I ran the Clear script, there still seemed to be some settings (like Lan IP) that were not cleared.

is there anything else I can do ? 

[DenbyWireless]

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.

How can I check this, the nvram all looks fine ?

[WorldSpot]

Do you still get auth_ok even with beta.5?
If you get auth_ok then there is a problem. Otherwise you should get STOPPED in your history.

[DenbyWireless]

Do you still get auth_ok even with beta.5?
If you get auth_ok then there is a problem. Otherwise you should get STOPPED in your history.

Yes, B5, B4, B4 w/patch.  Seems like no matter what I do.  I just PM'd you some additional info.
Would be great if you can help me fix this.

[DenbyWireless]

Just For clarity and to let people know the resolution to my AUTH_OK issues.
This definitely had something to do with the front end router connected to the internet.
I had it configured for DMZ to my IP running the HS software. When I did this, I constantly had this problem.

I set it up this way so I could remote admin. I'm not sure what caused this, but just hanging the HS router off the WAN connected router without DMZ resolved all these AUTH_OK problems. 

[DenbyWireless]

STOP_FORCED      2007-07-05 13:07:31

I've seen a few of these STOP_FORCED messages lately.

Is this a problem ? what does it mean ?
Thanks

[WorldSpot]

STOP_FORCED means that a user tried to connect to an existing session that is already connected on the same hotspot nasID, probably because chillispot has restarted, or the STOP request has not been received for any reason.
You may check your hotspot start time and see if it restarted.