Re: (RADIATOR) No Proxy-State Attribute After Max Session Exceeded Reply

2004-01-07 Thread Hugh Irvine
Hello Lee - You should test this with Radiator 3.8, which should work correctly. Please let me know if it doesn't. regards Hugh On 08/01/2004, at 4:56 PM, Lee Webb wrote: Hi, I have noticed that the Proxy-State attribute is not being preserved in the Access-Reject after a Max Sessions Exceed

(RADIATOR) No Proxy-State Attribute After Max Session Exceeded Reply

2004-01-07 Thread Lee Webb
Hi, I have noticed that the Proxy-State attribute is not being preserved in the Access-Reject after a Max Sessions Exceeded I was under the impression that Radiator would preserve the Proxy-State attribute {from ref.html Radiator automatically copies any Proxy-State attribute from the incoming Ra

Re: (RADIATOR) Problem with rewriteusername and chap

2004-01-07 Thread Hugh Irvine
Hello Chris - I believe the problem is to do with MS-CHAP V2 which uses the full username to check the password. Have a look at the comment header and the code in "Radius/MSCHAP.pm" in the Radiator 3.8 distribution. regards Hugh On 08/01/2004, at 5:18 AM, Chris Simmons wrote: Dear all, Fi

Re: (RADIATOR) Time Restriction

2004-01-07 Thread Nathan 'Franko' Franklin
Hugh,List I got it working, My data types were incorrect, here is what happened... I had my Time attribute datatype set at 1 (integer), which means in my RadConfigs tables for my customers it was looking at the integer value (an integer field) which had the value of 2. So i change the data type

(RADIATOR) Problem with rewriteusername and chap

2004-01-07 Thread Chris Simmons
Dear all, First, I must say sorry for the log post (and html). Secondly, we have a client  sending: username = [EMAIL PROTECTED] via MS-CAHP V2 and the password "password". We are running a simple config.file: RewriteUsername s/[EMAIL PROTECTED]//     Secret  mysecret