[RADIATOR] Trace level

[Heikki Vatiainen]

On 01/03/2014 02:11 PM, Judy Angel wrote:

> trace 3 only has userid

Hello Judy,

try using Trace 4 and add this global configuration parameter:

PacketDumpOmitAttributes EAP-Message

See the reference manual for more, but the above parameter allows you to
list any attributes that should not be in Trace 4 and 5 dumps.

It's a fairly recent addition, so if you are using Radiator older than
4.10 you would need to do what Alan suggests.

Thanks,
Heikki

> Judy
> 
> --On 03 January 2014 11:06 +0000 A.L.M.Buxey at lboro.ac.uk wrote:
> 
>> Hi,
>>
>>> I like the output of Trace 4, it makes it easy to check user inquiries
>>> as  it captures the username, IP, MAC, but the log files get very big
>>> due the  the verbose output from the EAP traffic. At the moment I just
>>> rotate the  log file a few times a day but is there a better way around
>>> that?
>>
>> Trace 3 doesnt provide required info?
>>
>> You could edit the Perl source to stop the logging of the EAP messages
>>
>> alan
>> _______________________________________________
>> radiator mailing list
>> radiator at open.com.au
>> http://www.open.com.au/mailman/listinfo/radiator
> 
> 
> 
> 
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
> 


-- 
Heikki Vatiainen <hvn 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 etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.