Unexpected Accounting proxy behaviour
I have the following in "acct_users": peter Called-Station-Id == "myrealm", Proxy-To-Realm := myproxy Now, with this configuration, "myproxy" receives all of the accounting packets (Start, Interim-Update and Stop) as expected, HOWEVER on the radius server doing the proxying in sqltrace.log (and in the SQL table) I only see the "Start" record. For non proxied packets I happily have the 3 different typs of SQL queries show up in sqltrace.log Can anyone tell me what is different about Start records that would cause this behaviour? I am running the 1.1.x branch cvs snapshot from 2006-08-08 on this server. Thanks in Advance -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
Peter Nixon wrote:
I have the following in "acct_users":
peter Called-Station-Id == "myrealm", Proxy-To-Realm := myproxy
Now, with this configuration, "myproxy" receives all of the accounting packets (Start, Interim-Update and Stop) as expected, HOWEVER on the radius server doing the proxying in sqltrace.log (and in the SQL table) I only see the "Start" record. For non proxied packets I happily have the 3 different typs of SQL queries show up in sqltrace.log
Can anyone tell me what is different about Start records that would cause this behaviour?
It should work. I'd suggest to double-check whether the NAS sends the Called-Station-Id attribute in "stop" and "alive" packets, too. -- Nicolas Baradakis
On Tue 22 Aug 2006 15:16, Nicolas Baradakis wrote:
Peter Nixon wrote:
I have the following in "acct_users":
peter Called-Station-Id == "myrealm", Proxy-To-Realm := myproxy
Now, with this configuration, "myproxy" receives all of the accounting packets (Start, Interim-Update and Stop) as expected, HOWEVER on the radius server doing the proxying in sqltrace.log (and in the SQL table) I only see the "Start" record. For non proxied packets I happily have the 3 different typs of SQL queries show up in sqltrace.log
Can anyone tell me what is different about Start records that would cause this behaviour?
It should work.
Yes. I know, however unfortunately it does not :-(
I'd suggest to double-check whether the NAS sends the Called-Station-Id attribute in "stop" and "alive" packets, too.
It does. Can someone please try the same config and see if they can reproduce the bug? -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
participants (2)
-
Nicolas Baradakis -
Peter Nixon