[RADIATOR] COA log

[Michael]

I personally log COA/POD requests using a very custom method.  This may 
not be desirable for others.  I do this by after processing the COA/POD 
normally, pass it to an AuthBy config that essentially changes it to an 
Accounting-Request packet, populates a few extra values, then passes it 
to my normal accounting log AuthBy.  This also requires adding custom 
values to the dictionary file.


<AuthBy GROUP>
          Identifier convert2accounting

         <AuthBy INTERNAL>
                 OtherHook sub {\
                   # some fancy code here.
                 }
         </AuthBy>

         # now that this packate has been converted to an accounting 
packet, it is ready to be logged.  pass it to the accounting log AuthBy
         AuthBy accounting_log
</AuthBy>


an example result is something like this:

+----------+---------------------+--------+-----------+--------------+
| username | timestamp           | type   | sess_time | term_cause   |
+----------+---------------------+--------+-----------+--------------+
| username | 2015-01-05 15:04:09 | login  |      NULL | NULL         |
| username | 2015-01-05 16:46:03 | info   |      NULL | rate-change  |
| username | 2015-01-05 16:47:02 | info   |      NULL | kick-request |
| username | 2015-01-05 16:47:02 | logout |      6173 | Admin-Reset  |
+----------+---------------------+--------+-----------+--------------+





On 04/02/15 05:57 PM, Hugh Irvine wrote:
> Hello -
>
> As COA is not an authentication, it therefore follows that it will not be logged by an AuthLog clause.
>
> To see what happens with a COA you will need to look at the log file (not the authlog file).
>
> regards
>
> Hugh
>
>
>> On 4 Feb 2015, at 20:49, ONRUBIA AVILES Carlos (SPC/CSP) <carlos.onrubia.aviles at proximus.com> wrote:
>>
>> Dear all,
>>
>>   
>>
>> I have the following problem:
>>
>>   
>>
>> I can log authentification with the configuration here below,  it works correctly.
>>
>> But if I use event_log identifier to log a COA (and not a normal  Access-Request with Accept or Reject), nothing happens.
>>
>>   
>>
>> Can you indicate me how to log a COA with the answer (ACK or NACK)
>>
>>   
>>
>> Thanks in advance,
>>
>>   
>>
>>   
>>
>>   
>>
>> <Handler User-Name = ABCD
>>
>>      AuthBy              toto
>>
>>      AuthLog             event_log
>>
>> </Handler>
>>
>>   
>>
>> <AuthLog FILE>
>>
>>      Identifier          event_log
>>
>>      Filename            %L/event_auth.log
>>
>>      SuccessFormat       %v %d %H:%M:%S,,%s,,%n,,HIDDEN,,%a,,PASS,,%N,,%c,,%{Type},,%{Connect-Info},,%{Calling-Station-Id},,%{GlobalVar:servername}%{GlobalVar:suffixfon},,%{GlobalVar:authPort},,
>>
>>      FailureFormat       %v %d %H:%M:%S,,%s,,%n,,HIDDEN,,none,,FAIL,,%N,,%c,,%{Type},,%{Connect-Info},,%{Calling-Station-Id},,%{GlobalVar:servername}%{GlobalVar:suffixfon},,%{GlobalVar:authPort},,%1
>>
>>      LogSuccess          1
>>
>>     LogFailure          1
>>
>> </AuthLog>
>>
>>   
>>
>>   
>>
>>   
>>
>>   
>>
>>   
>>
>>
>>
>> ***** Disclaimer *****
>> http://www.proximus.be/maildisclaimer
>> _______________________________________________
>> radiator mailing list
>> radiator at open.com.au
>> http://www.open.com.au/mailman/listinfo/radiator
>
> --
>
> Hugh Irvine
> hugh at open.com.au
>
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
> TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
> DIAMETER, SIM, etc.
> Full source on Unix, Linux, Windows, MacOSX, Solaris, VMS, NetWare etc.
>
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
>