(RADIATOR) AuthBy LDAP2 behavior when LDAP server is down.

When the LDAP server that is defined in an AuthBy LDAP2 clause is down Radiator returns an Access-Reject User database access error. It would be better if it timed out so Radiator could use another AuthBy clause or discarded the request. This is how Radiator behaves when the LDAP server gets a

Re: (RADIATOR) AuthBy LDAP2 behavior when LDAP server is down.

Ignore my request. I figured it out myself. Regards Vangelis Vangelis Kyriakakis wrote: When the LDAP server that is defined in an AuthBy LDAP2 clause is down Radiator returns an Access-Reject User database access error. It would be better if it timed out so

(RADIATOR) Attribute not found

I'm faily new to Radiator but have it running locally. I am going to wholesale dialup and during testing I'm getting: ERR: Attribute number 151 is not defined in your dictionary This is coming from a Cisco RAS. I have a number 151's in my dictionary file, but apparently they aren't the correct

RE: (RADIATOR) Attribute not found

According to the Cisco docs at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/csn t2/ap_rads.htm atrribute 151 is Ascend-Session-Svr-Key, it should also be in the dictionary.ascend file that came with the Radiator distribution. So your dictionary should have a line in it

(RADIATOR) time billing issues

Hi all, This is not a specific Radiator issue (at least I don't think it is) but I thought this mailing list could help We are migrating to a new billing system and so we have run the new system in parallel with the old for last month's billing cycle. We have found that they are producing

Re: (RADIATOR) time billing issues

Hello Greg - You are correct - if you lose a stop, you lose everything if your billing is based on stops only. Obviously, a system that takes into account Alives will be more accurate. The other difference to check is the difference between the start and stop timestamps, and the time

re[2]: (RADIATOR) Attribute not found

-- Forwarded Message -- Subject: BOUNCE [EMAIL PROTECTED]:Non-member submission from [Matt Taylor [EMAIL PROTECTED]] Date: Tue, 3 Dec 2002 13:40:17 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] From [EMAIL PROTECTED] Tue Dec 3 13:40:17 2002 Received: from

Re: re[2]: (RADIATOR) Attribute not found

Hello Matt - As Frank shows below, you need to add the attribute to the dictionary file that you have configured and restart Radiator so it is re-read. Note that there is also a vendor-specific version of this same attribute if you are using the Ascend vendor-specifics. regards Hugh