Ciao Paulo -
In this case I would suggest you use a SessionDatabase SQL clause.
See section 5.10 in the Radiator 4.10 reference manual ("doc/ref.pdf").
regards
Hugh
On 21 Oct 2012, at 07:45, Paolo Di Francesco <[email protected]>
wrote:
> Hi Hugh
>
> yes that seems the right direction. At the same time it would be helpful also
> change the format, i.e. what is recorded in the file in oder to take only the
> information that I need.
>
> I have seen that I can change the format with the command AcctLogFileFormat
> but I do not find the whole list of strings to complete the "line" that I
> want to print.
>
> In addiction to the following
>
> AcctLogFileFormat %{Timestamp} %{Acct-Session-Id}\
> %{User-Name}
>
> I would like to record also the following variables:
>
> - user-IP: the IPv4 or IPv6 address for this session
> - if the user is getting or leaving this IP
>
> so it should be ok to keep track of IPs allocated to users in the system
>
> Moreover I would NOT to record all the messages that I get right now, because
> at the moment I get also the Alive packets (Acct-Status-Type = Alive ) which
> makes the log huge (if every N seconds I log an Alive packet from each
> customer/NAS the log will grow quickly).
>
> Thank you.
>
> >
>> Ciao Paolo -
>>
>> As you have seen, the debug log is not what you want.
>>
>> Rather, you should be using the RADIUS accounting requests to write to a
>> file.
>>
>> You can have a separate file for each user by doing something like this:
>>
>>
>> # Realm or Handler
>>
>> <Handler ….>
>>
>> AcctLogFileName %L/accounting-for-%n
>>
>> …..
>>
>> <Handler>
>>
>>
>> Of course, your NAS equipment must be configured to send RADIUS accounting
>> requests.
>>
>> See sections 5.2, 5.19.4 and 5.19.5 in the Radiator-4.11 reference manual
>> ("doc/ref.pdf").
>>
>> regards
>>
>> Hugh
>>
>>
>> On 18 Oct 2012, at 02:02, Paolo Di Francesco <[email protected]>
>> wrote:
>>
>>> Dear All
>>>
>>> in oder to keep track of the user getting in and getting out of my
>>> network I would like to do the following: let radiator write into a file
>>> (mounted on some linux syslogd) when a user is getting into the network
>>> and when the user is leaving.
>>>
>>> I found the log file command but not sure it does what I want (i.e.
>>> record the user login/logout). It looks more like a more verbose logging
>>> facility but I would like to know if you can point me in the right direction
>>>
>>> thank you
>>>
>>> --
>>>
>>>
>>> Ing. Paolo Di Francesco
>>>
>>> Level7 s.r.l. unipersonale
>>>
>>> Sede operativa: Largo Montalto, 5 - 90144 Palermo
>>>
>>> C.F. e P.IVA 05940050825
>>> Fax : +39-091-8772072
>>> assistenza: (+39) 091-8776432
>>> web: http://www.level7.it
>>>
>>>
>>>
>>> _______________________________________________
>>> radiator mailing list
>>> [email protected]
>>> http://www.open.com.au/mailman/listinfo/radiator
>>
>>
>> --
>>
>> Hugh Irvine
>> [email protected]
>>
>> 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 etc.
>> Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc.
>>
>>
>
>
> --
>
>
> Ing. Paolo Di Francesco
>
> Level7 s.r.l. unipersonale
>
> Sede operativa: Largo Montalto, 5 - 90144 Palermo
>
> C.F. e P.IVA 05940050825
> Fax : +39-091-8772072
> assistenza: (+39) 091-8776432
> web: http://www.level7.it
>
>
>
--
Hugh Irvine
[email protected]
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 etc.
Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc.
_______________________________________________
radiator mailing list
[email protected]
http://www.open.com.au/mailman/listinfo/radiator
