Small issue with buffered-sql

[Alex Sharaz]

Got a small problem with the use of buffered-sql virtual server . I've been
moving over to using this in an attempt to being a bit more considerate of
our postgresql database which currently has 6 FR 3.0.12 systems
concurrently updating my freeraidus database.

The following problem is present in both 3.0.12 and a 3.0.13  systems.

Initially I replaced the -sql statements in my inner-tunnel virt server
with a call to detail  and that worked just fine. I then tried to the same
thing with my "default" virtual host so that proxied auths for visiting
eduroam users would use buffered-sql as well.  As soon as I did this (this
was trying to use buffered sql for post-auth and accounting packets
although the details.work file continued to grow, it never came down.
Looking at contents of details.work, the 1st thing I noticed was that while
Authentication packets had a Packet-Type = Access-Request just after the
timestamp, Accounting packets didn't have a Packet-Type attribute.

Accounting packet

Fri Nov 25 09:09:14 2016
        User-Name = "@leicester.ac.uk"
        NAS-IP-Address = 144.32.64.38
        NAS-Port = 0
        NAS-Port-Type = Wireless-802.11
        Acct-Session-Id = "@leicestA8667F143971-5837FD04"
        Event-Timestamp = "Nov 25 2016 09:08:54 GMT"
        Acct-Multi-Session-Id = "A8667F143971-0013936352"
        Framed-IP-Address = 10.241.6.100
        Calling-Station-Id = "A8-66-7F-14-39-71"
        Called-Station-Id = "00-1A-1E-00-C9-00"
        Class =
0xa79cda48d0da4a94a13fcfdcc173bd24ba0b0000040000005230313332326633632d32342d35383337666431340000000000000000000000
        Acct-Delay-Time = 20
        Aruba-Essid-Name = "eduroam"
        Aruba-Location-Id = "coheeap28"
        Aruba-AP-Group = "Constantine"
        Aruba-User-Role = "authenticated"
        Aruba-User-Vlan = 3865
        Aruba-Device-Type = "OS X"
        Acct-Status-Type = Interim-Update
        Acct-Input-Octets = 48797
        Acct-Output-Octets = 123431
        Acct-Input-Packets = 310
        Acct-Output-Packets = 249
        Acct-Session-Time = 674
        NAS-Identifier = "aruba0"
        Proxy-State = 0x323039
        FreeRADIUS-Acct-Session-Start-Time = "Nov 25 2016 08:57:40 GMT"
        Module-Failure-Message = "regex failed: Found null in subject at
offset 18.  String unsafe for evaluation"
        Module-Failure-Message = "Failed retrieving values required to
evaluate condition"
        Acct-Unique-Session-Id = "4d4f17755ded442a500b90bded7f1746"
        Stripped-User-Name = ""
        Realm = "DEFAULT"
        Timestamp = 1480064954

Access-Request packet

Fri Nov 25 09:09:15 2016
        Packet-Type = Access-Request
        User-Name = ""
        Calling-Station-Id = ""
        NAS-IP-Address = 10.237.0.3
        NAS-Port = 164
        Called-Station-Id = ""
        Service-Type = Framed-User
        Framed-MTU = 1400
        NAS-Port-Type = Wireless-802.11
        NAS-Identifier = "2"
        Connect-Info = "CONNECT 802.11g/n"
        EAP-Message =
        Ruckus-SSID = "eduroam"
        Message-Authenticator = 0x6d912a50a69db5ec8e97fe20d8a281e5
        Event-Timestamp = "Nov 25 2016 09:09:15 GMT"
        Called-Station-SSID = "eduroam"
        SQL-User-Name = ""
        Realm = "eduroam"
        Operator-Name = "1york.ac.uk"
        Chargeable-User-Identity = 0x00
        EAP-Type = Identity
        Timestamp = 1480064955


Removing all references to using detail in my default virtual server but
using it in my inner-tunnel server returned things to normal all my servers
I made the change to.

Should I be able to use buffered-sql to process accounting packets?

Rgds
Alex