detail sql logging problem

[A.L.M.Buxey at lboro.ac.uk]

hi,

further to last email, heres example packet:

Tue Apr 15 12:20:56 2008
        User-Name = "xxxxx"
        NAS-Port = 29
        NAS-IP-Address = 192.168.1.28
        Framed-IP-Address = 192.168.0.3
        NAS-Identifier = "wism"
        Airespace-Wlan-Id = 1
        Acct-Session-Id = "48048f97/00:11:12:12:14:11/8514"
        Acct-Authentic = RADIUS
        Tunnel-Type:0 = VLAN
        Tunnel-Medium-Type:0 = IEEE-802
        Tunnel-Private-Group-Id:0 = "222"
        Acct-Status-Type = Stop
        Acct-Input-Octets = 1942107
        Acct-Output-Octets = 5085070
        Acct-Input-Packets = 9162
        Acct-Output-Packets = 8299
        Acct-Terminate-Cause = Lost-Service
        Acct-Session-Time = 0
        Acct-Delay-Time = 0
        Calling-Station-Id = "192.168.0.3"
        Called-Station-Id = "192.168.1.28"
        Acct-Unique-Session-Id = "f7ebd89424c03437"
        Timestamp = 1208258456
        Request-Authenticator = Verified

as you can see, Stop request, due to lost service.  however, sessio-time
is 0 - i suspect this is because of mobility. they've moved from one
wism controller to another or from one AP to another and then left
the network altogther. either way, kit is reporting the value. in
our SQL logging we look for the Acct-Session-Id, and the Timestamp
and then use those to create the session time due to wierdnesses
(see the example UPDATE comand in sql/postgresl/dialup.conf to get
what I mean) so hope we dont actually care about what the kit tells
us(!)

alan