[VOPRadius] Authentication Problems

[Gary Carr]

In the lucent box it is called checkpoint not watchdog and it is located under external-auth         Gary   ----- Original Message ----- From: Drew Salmon To: [EMAIL PROTECTED] Sent: Monday, June 23, 2003 11:39 AM Subject: [VOPRadius] Authentication Problems I would also be interested in this info.  We have 9 Ascend NAS boxes and we only have this same problem with two of them.   Go figure?   Thanks, Drew   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Essary Sent: Monday, June 23, 2003 8:59 AM To: [EMAIL PROTECTED] Subject: [VOPRadius] Authentication Problems   Any idea where in the Lucent/Ascend MAX unit software this watch dog setting is located for  ? Larry To setup the NAS and VOP Radius to use the Watchdog/Interim packets: Consult the NAS manufacturer to confirm that it is possible. There are hundreds of NAS manufacturers and it is not possible for use to list the exact configuration here. Set the Interval time that the Watchdog packet will be sent (e.g. once every 3 minutes) Confirm that VOP Radius is receiving the Watchdog packets. You can do this by using  the VPRError.log and locating an Accounting Packet. The value of the Acct-Status-Type Attribute (40) will equal "Watchdog" and/or an integer value of 3. Open the VOP Radius Control Panel-->Clients Tab and select the Client definition for the NAS. On the bottom left there should be a setting called "Interval time between Interim packets [sec]" Enter a value here that is at least 3 times greater compared to what was set in the NAS (e.g. 9 minutes). The reason we set the Interval time greater in VOP Radius is because we do not want to prematurely remove the username from the Users Online Listing. Accounting Watchdog packets like Stop packets do go missing. There s an article available on Vircom s website detailing how to help prevent this from occurring. http://www.vircom.com/L0g1n/Vircom_Clients/Howtos/howto/howtovoprad_016.asp I have a problem with VOPRadius in that sometimes it doesn't release users that have logged off meaning if the same user tries to logon, they get an " invalid username/password" error, and I get the " simultaneous login exceeded" in error logs.