Re: (RADIATOR) Acct-Session-Id Error

2002-10-28 Thread Hugh Irvine
Hello Doug - Have you restarted Radiator to re-read the dictionary? Are you sure you have changed the correct dictionary? I am actually surprised that Radiator is trying to use Acct-Session-Id as an integer in any case - it should be a string. And changing the dictionary definition results in

Re: (RADIATOR) Acct-Session-Id Error

2002-10-28 Thread Doug Clements
That did not seem to do much.. I'm still getting the errors. The secondary problem we have is that since Radiator is assuming the Acct-Session-Id is 0, then people for whom we proxy radius to are getting 0 for this value, and can't track their users. Is there a way to force Radiator to "cast" t

Re: (RADIATOR) Acct-Session-Id Error

2002-10-25 Thread Hugh Irvine
Hello Doug - This is actually a NAS problem, due to a recent upgrade to the CVX software. The Acct-Session-Id is defined as a string (check the RFC), and the CVX is now sending binary data instead. You should check with your vendor to find out what they are sending and how to interpret it.

(RADIATOR) Acct-Session-Id Error

2002-10-24 Thread Doug Clements
Greetings. I'm getting the following error in my radius log: Thu Oct 24 11:21:38 2002: ERR: There is no value named Á-#ר² for attribute Acct-Session-Id. Using 0. Thu Oct 24 11:23:13 2002: ERR: There is no value named Á-#×Ôo for attribute Acct-Session-Id. Using 0. Thu Oct 24 11:23:21 2002: ERR: