accounting

John Martins jm829580 at gmail.com
Tue Jul 3 00:46:45 CEST 2018


Hello,
Below the info. required.


accounting {
        #  Update accounting packet by adding the CUI attribute
        #  recorded from the corresponding Access-Accept
        #  use it only if your NAS boxes do not support CUI themselves
#       cui
        #
        #  Create a 'detail'ed log of the packets.
        #  Note that accounting requests which are proxied
        #  are also logged in the detail file.
        detail
#       daily

        #  Update the wtmp file
        #
        #  If you don't use "radlast", you can delete this line.
        unix

        #
        #  For Simultaneous-Use tracking.
        #

        #
        #  Due to packet losses in the network, the data here
        #  may be incorrect.  There is little we can do about it.
#       radutmp
#       sradutmp

        #  Return an address to the IP Pool when we see a stop record.
#       main_pool

        #
        #  Log traffic to an SQL database.
        #

        #  See "Accounting queries" in mods-available/sql
        sql

        #
        #  If you receive stop packets with zero session length,
        #  they will NOT be logged in the database.  The SQL module
        #  will print a message (only in debugging mode), and will
        #  return "noop".
        #
        #  You can ignore these packets by uncommenting the following
        #  three lines.  Otherwise, the server will not respond to the
        #  accounting request, and the NAS will retransmit.
        #
#       if (noop) {
#               ok
#       }

        #  Cisco VoIP specific bulk accounting
#       pgsql-voip

        # For Exec-Program and Exec-Program-Wait
        exec

        #  Filter attributes from the accounting response.
        attr_filter.accounting_response

        #
        #  See "Autz-Type Status-Server" for how this works.
        #
#       Acct-Type Status-Server {
#
#       }
}


thanks)


On Mon, Jul 2, 2018 at 9:41 PM, John Martins <jm829580 at gmail.com> wrote:

> Hello,
>
> My freeradius 3.0.16 is not inserting data into radact, and it complains
> on start with the following error, but the accounting section is in
> radiusd.conf as stated below. Can anybody give me a clue where can be the
> problem?
>
> accounting {
>         # We leave "detail" enabled to _additionally_ log accounting to
> /var/lo$
>         detail
>         sql
> }
>
>
> Error on freeradius Start:
>
> /etc/freeradius/3.0/radiusd.conf[784]: The accounting section should be
> inside of a 'server { ... }' block!
>
> thanks
>
> Best
>
>


More information about the Freeradius-Users mailing list