(RADIATOR) Logging Question

[Hugh Irvine]

Hello Bret -

You may need to use the PacketTrace parameter in the various clauses to  
control what happens.

See section 6.5.17 in the Radiator 3.9 reference manual.

You may also need to set the golbal trace level to 4: Trace 4.

Note that the logging is additive - the global log is written first,  
then any other logging is done.

Of course if you find that something is broken please let us know.

BTW- you may also find it useful to have Radar and/or your own  
application to connect to the Monitor port.

Alternatively you could set up a first level Radiator that then proxies  
to target Radiator instances based on your Handlers. Then the  
individual instances can do different logging however you wish. Also  
note that you can alter the trace level dynamically by sending USR1 and  
USR2 signals.

regards

Hugh


On 1 Apr 2004, at 17:15, Bret Jordan wrote:

> I am wondering if it is possible to setup two different Loggers and  
> then just point certain handlers to certain loggers where the loggers  
> are defined globally (what I am seeing is that all the handlers use  
> the last defined logger rather than the one I have definied for them).  
>  Example:  somewhere.com should have trace level 4 logging while  
> somethingelse.com has trace level 3 logging.    I am using 3.8 btw.
>
> Thanks
> Bret
>
>
> # Global Config
>
> # ----------------------------------------
> # Logging
> # ----------------------------------------
> #LogStdout
> LogDir                  /var/log/radiator
> LogFile                 %L/radiator.log
>
> <Log FILE>
>    Identifier          Logger_System
>    Trace               3
>    Filename            %L/radiator.log
> </Log>
>
> <Log FILE>
>    Identifier          Logger_System_Debug
>    Trace               4
>    Filename            %L/radiator_debug.log
> </Log>
>
>
>
> # Handlers Section
> <Handler  
> Realm=somewhere.com,Client-Identifier=/ 
> Wireless_AccessPoint|Radius_Mesh/>
>    RejectHasReason
>    AcctLogFileName             %L/somewhere.com_accounting.log
>    AcctLogFileFormat           %l, %{User-Name}, %{Acct-Session-Id},  
> %{Acct-Authentic}, \
>                                %{Acct-Status-Type}, %{NAS-Identifier},  
> %{NAS-IP-Address}, \
>                                %{NAS-Port}, %{NAS-Port-Type},  
> %{Timestamp}
>
>    #PasswordLogFileName        %L/somewhere.com_login.log
>    Log                         Logger_System_Debug
>    AuthLog                     Logger_Authentication
>
>    RewriteUsername s/^([^@]+).*/$1/
>    <AuthBy FILE>
>        Filename                        %D/somewhere.com_users
>        EAPTLS_SessionResumption        0
>        EAPType                         TTLS TLS
>        EAPTLS_MaxFragmentSize          1024
>        EAPTLS_CAFile                   %D/cert/root.pem
>        EAPTLS_CertificateType          PEM
>        EAPTLS_CertificateFile          %D/cert/server-cert.pem
>        EAPTLS_PrivateKeyFile           %D/cert/server-cert.pem
>        EAPTLS_PrivateKeyPassword        
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>        #EAPTLS_RandomFile              %D/cert/random
>        AutoMPPEKeys
>    </AuthBy>
> </Handler>
>
> <Handler  
> Realm=somethingelse.com,Client-Identifier=/ 
> Wireless_AccessPoint|Radius_Mesh/>
>    RejectHasReason
>    AcctLogFileName             %L/somethingelse.com_accounting.log
>    AcctLogFileFormat           %l, %{User-Name}, %{Acct-Session-Id},  
> %{Acct-Authentic}, \
>                                %{Acct-Status-Type}, %{NAS-Identifier},  
> %{NAS-IP-Address}, \
>                                %{NAS-Port}, %{NAS-Port-Type},  
> %{Timestamp}
>
>    #PasswordLogFileName        %L/somethingelse.com_login.log
>    Log                         Logger_System
>    AuthLog                     Logger_Authentication
>
>    RewriteUsername s/^([^@]+).*/$1/
>    <AuthBy FILE>
>        Filename                        %D/somethingelse.com_users
>        EAPTLS_SessionResumption        0
>        EAPType                         TTLS TLS
>        EAPTLS_MaxFragmentSize          1024
>        EAPTLS_CAFile                   %D/cert/root.pem
>        EAPTLS_CertificateType          PEM
>        EAPTLS_CertificateFile          %D/cert/server-cert.pem
>        EAPTLS_PrivateKeyFile           %D/cert/server-cert.pem
>        EAPTLS_PrivateKeyPassword        
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>        #EAPTLS_RandomFile              %D/cert/random
>        AutoMPPEKeys
>    </AuthBy>
> </Handler>
>
> -- 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Bret Jordan                       Dean's Office
> Director of Networking   College of Engineering
> 801.585.3765                 University of Utah
>            jordan at coe.utah.edu
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> --
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
>
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.