Hello all, We're using freeradius 2.0.5 in our test environment and noticed that our detail record doesn't have "Freeradius-Proxied-To" information like our current production radius which is still running an old version of freeradius. We currently setup the accounting record to be proxied to a remote radius server and running in debug mode showed that the accounting record was being sent to remote server but nothing in detail record. Is this something I have to specify on a config file? Cheers, Roy Kartadinata
Hi
We're using freeradius 2.0.5 in our test environment and noticed that our detail record doesn't have "Freeradius-Proxied-To" information like our current production radius which is still running an old version of freeradius. We currently setup the accounting record to be proxied to a remote radius server and running in debug mode showed that the accounting record was being sent to remote server but nothing in detail record. Is this something I have to specify on a config file?
You can easily add that functionality using unlang: pre-proxy { update proxy-request { Freeradius-Proxied-To := "%{control:Proxy-To-Realm}" } detail_local } kind regards Pshem
Hi Pshem, I tried your suggestion but still didn't work. Any other suggestion? Cheers, Roy Kartadinata -----Original Message----- From: freeradius-users-bounces+rkartadinata=pocket.com@lists.freeradius.org [mailto:freeradius-users-bounces+rkartadinata=pocket.com@lists.freeradiu s.org] On Behalf Of Pshem Kowalczyk Sent: Wednesday, July 09, 2008 4:25 PM To: FreeRadius users mailing list Subject: Re: detail records Hi
We're using freeradius 2.0.5 in our test environment and noticed that our detail record doesn't have "Freeradius-Proxied-To" information like our current production radius which is still running an old version of freeradius. We currently setup the accounting record to be proxied to a remote radius server and running in debug mode showed that the accounting record was being sent to remote server but nothing in detail record. Is this something I have to specify on a config file?
You can easily add that functionality using unlang: pre-proxy { update proxy-request { Freeradius-Proxied-To := "%{control:Proxy-To-Realm}" } detail_local } kind regards Pshem - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
We only missing "Freeradius-Proxied-To" attribute which is the most important one. Below is what we have for accounting setting: Accounting { detail sql } Cheers, Roy Kartadinata -----Original Message----- From: freeradius-users-bounces+rkartadinata=pocket.com@lists.freeradius.org [mailto:freeradius-users-bounces+rkartadinata=pocket.com@lists.freeradiu s.org] On Behalf Of Pshem Kowalczyk Sent: Thursday, July 10, 2008 5:13 PM To: FreeRadius users mailing list Subject: Re: detail records Hi,
I tried your suggestion but still didn't work. Any other suggestion?
Does anything get logged at all? Or are they only missing the additional attribute? kind regards Pshem - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
We only missing "Freeradius-Proxied-To" attribute which is the most important one.
Below is what we have for accounting setting:
Accounting { detail sql }
You have to do the logging in the pre-proxy section of the proxy server, otherwise the server doesn't know yet that it will be proxing the packet (I guess you could do that in the accounting section, but _after_ the decision is made to proxy the packet). ATM you log the packet just after you've received it. So obviously it's a vanilla packet that you got from your NAS. kind regards Pshem
participants (3)
-
Alan DeKok -
Pshem Kowalczyk -
Roy Kartadinata