Hello,

I understand that the acct-session-id is unique to each session. However, if
in the following scenario,

' Local request' -->Radiator A  <-- Roaming Radiator <-- Other Radius <--
'Proxy request'

How would Radiator A acct-session-id be assigned in the case of 'Local
request' as opposed to the 'Proxy request'?
 Would the acct-session-id in the 'Proxy request' being assigned by the
Other Radius, whilst acct-session-id of the 'Local request' being assigned
by Radiator A. Is there a chance that Radiator A would have two accounting
records with same acct-session-id?

Secondly, from the accounting record, there is a field known as Proxy-state.
It is mentioned in the RFC2138 Sec 5.33 that it is implementation dependent.
So, how is this Proxy-state being implemented in Radiator? And how do I
interpret the information contained in the Proxy-state?

Thanks in advance.

Jason Cheung




===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to