Logging proxy server

[Chris Taylor (chtaylo2)]

Thanks, however I’ve tried that before and received errors. Here I’ve tried two ways, both failing:

 

(0) ERROR: [Source: %{NAS-IP-Address}] [Proxy: %{proxy:Packet-Dest-IP-Address}]

(0) ERROR:                                       ^ Unknown module

 

(2) ERROR: [Source: %{NAS-IP-Address}] [Proxy: %{Packet-Dest-IP-Address}]

(2) ERROR:                                       ^ Unknown attribute

 

 

 

 

On 2/2/17, 6:40 PM, "Freeradius-Users on behalf of Alan DeKok" <freeradius-users-bounces+chtaylo2=cisco.com at lists.freeradius.org on behalf of aland at deployingradius.com> wrote:

 

    On Feb 2, 2017, at 6:24 PM, Chris Taylor (chtaylo2) <chtaylo2 at cisco.com> wrote:

    > 

    > 1.)     Is it possible to log the home_server which proxied a connection? 

    > 

    > 

    > Log today: 

    > 

    > radiusd[22590]: (436) Login OK: [Radius-ACE-Prob at REMOTE] (from client Radius-ACE-Prob port 0) [Source: 111.111.111.111]

    

      See raddb/radiusd.conf.  Look for "msg_goodpass"

    

      You can add %{proxy:Packet-Dest-IP-Address} there along with other text. 

    

    > I’d like to be able to log --> [Proxy: home_server_A].

    > 

    > If not possible there, how about in 

    > 

    > post-proxy {

    > 

    > post_proxy_log  

    

      You can do that with the linelog module, and %{proxy:Packet-Dest-IP-Address}.

    

      Alan DeKok.

    

    

    -

    List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4054 bytes
Desc: not available
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20170203/788c2573/attachment.bin>