Freeradius-Users Digest, Vol 135, Issue 39

[Peter Hutchison]

>> e.g.
>> Mon Jul 18 08:38:00 2016 : Auth : [U1234567 at hud.ac.uk] (from client roaming0.ja.net port 0 via TLS tunnel).
>> Instead of
>> Mon Jul 18 08:38:00 2016 : Auth : [U1234567 at hud.ac.uk] (from client qsa.n2k-mc01 port 0 via TLS tunnel).

> umm, the only difference there is the NAS client name


>and this doesnt look like linelog - this looks like the default FreeRADIUS log file (in terms of layout and format
>- ie /var/log/radius/radius.log  or whereever your debian/ubuntu variant logs to/from.


>yuor question seems to have a level of confusion with it...the former entry could appear if a user logged in from a remote site (ie >requests came from one of the national proxies). the later would be a local login...in which case what do you currently see?

>for custom logging, use line log module, ensure the strings contain the things you need and call it where needed in the config as >required. if you need several types of logging formats, use named modules eg

>instead of

>linelog {
>stuff here
>}

>do

>linelog internal-log {
>stuff here
>}

>and call

>internal-log in whichever virtual server you needed that to be called  (perhaps eg inner-tunnel post-auth section).

I already have a custom linelog module called eduroam-logging with these entries

Linelog f_ticks { ... }

Linelog eduroam_log { ... }

Linelog inner_auth_log { .... }

The eduroam_log modules is called from the eduroam site in three places:
Accounting
Post-auth
  Post-Auth-Type REJECT

If it's using the default logging, how do I stop it from using that?



Peter Hutchison MCP
Senior Network Systems SpecialistS
S 01484 473716
Infrastructure Team
University of Huddersfield | Queensgate | Huddersfield | HD1 3DH


University of Huddersfield inspiring tomorrow's professionals.
[http://marketing.hud.ac.uk/_HOSTED/EmailSig2014/EmailSigFooter.jpg]

This transmission is confidential and may be legally privileged. If you receive it in error, please notify us immediately by e-mail and remove it from your system. If the content of this e-mail does not relate to the business of the University of Huddersfield, then we do not endorse it and will accept no liability.