Hi Alan,

 

In my actual deployment I have Radius client, RADIUS proxy and RADIUS Server.

 

Accounting-Request is originated form Radius client after success-full authentication.

Accounting request authenticator is generated using RADIUS proxy secret in RADIUS client.

RADIUS proxy functionality is to forward Accounting request to Remote Accounting server.

While doing proxy functionality Accounting-Request authenticator is re-calculated using Remote Accounting server secret

and updates he request with re-calculated value and the request is posted to remote end.

 

Please tell me whether my understanding about Accounting-Request authenticator and secret is correct.

 

Regards,

Karthik


Karthikeyan Gopal - ERS, HCL Tech wrote:

> *My config:*

> *NAS shared secret = testing123*

> *Accounting server Secret = 123testing*

 

  The NAS is sending accounting packets, too.  There is no "NAS" secret

and "accounting" secret.  There may be different secrets for

authentication and accounting, but the NAS will send both packets.

 

  Alan DeKok.

 


size=2 width="100%" align=center>

Hi,

 

I have one basic question in generating Accounting-Request and Response Authenticator generation.

 

My config:

NAS shared secret = testing123

Accounting server Secret = 123testing

 

While generating Accounting-Request Authenticator which secret to use?

NAS or Acct server secret?

 

In Accounting Response: Which secret should be used to generate accounting response authenticator?

 

Regards,

Karthik

 

DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. 
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in 
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. 
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of 
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have 
received this email in error please delete it and notify the sender immediately. Before opening any mail and 
attachments please check them for viruses and defect.

-----------------------------------------------------------------------------------------------------------------------