(RADIATOR) ISDN fails but Analog fine

Hi all, An 'upstream' radius server is our dialup proxy and sends us access requests. We are using radiator 3.3.1 With no change to our system we are having problems with ISDN customers for the last couple of days. There is no logging in Radius even at trace level 4 but TCPdump reports the

Re: (RADIATOR) ISDN fails but Analog fine

Hello Greg - I will need to see a hex packet dump from TCPdump together with a trace 5 debug from Radiator. regards Hugh On Friday, Apr 4, 2003, at 17:46 Australia/Melbourne, Greg 'Rafiq' Clarkson wrote: Hi all, An 'upstream' radius server is our dialup proxy and sends us access

(RADIATOR) Support of accountingmodus only + modification

Hello all, I'm trying to verify if Radiator (from which version on?), supports accounting modus only (start, stop, interim tickets) including the following additional feature(s): - Can we use attribute 40 (Accounting-Status-Type) with the value of 6 indicating for the billingprocess it

RE: (RADIATOR) Support of accountingmodus only + modification

-Original Message- From: Karel van der Velden Hello all, I'm trying to verify if Radiator (from which version on?), supports accounting modus only (start, stop, interim tickets) including the following additional feature(s): Well, at least back to something like 2.13; i.e.

(RADIATOR) Log accounting to a detail file

I have the following radius.conf file running on RedHat Linux 8.0 icw openldap I thought using the AcctLogFileName option, log information would be write to the detail file. Nothing happens although all the rights are open in the named directory. (The LogFile works fine). Whats wrong

(RADIATOR) MSCHAP-V2 and LDAP Clarification

Tom Riziom's response to my PEAP problem indicates that PEAP may not work wirh LDAP as noted below: btw. PEAP-MSCHAPV2 is not supported by an LDAP encrypted database, will need to use clear-text (EAP-TTLS-PAP for example). My understanding that as long as I have an LDAP with MD5 passwords I

(RADIATOR) AddToReply and Hosts

I am attempting to use the AddToReply and StripFromReply on a per host basis with SQLRADIUS and am not having much luck... Upon looking at the source code and the archives it looks like it should work... Here are the relevant pieces of my config, I am almost certain I am doing it correctly.

RE: (RADIATOR) ISDN fails but Analog fine

What brand NAS do you use? We found that with Cisco NASes (5300's, eg), some ISDN people had problems getting the PPP connection up, even after passing authenication (I guess IPCP was failing). Strangely, it seemed that if we took out the Idle-Timeout reply item attribute, lots of these people

Re: (RADIATOR) AddToReply and Hosts

Hello Miko - No this won't work. As you have discovered, AddToReply and StripFromReply will not work in a Host .. clause. I think you will need to use a ReplyHook to manipulate the proxy reply. You will find some example hooks in the file goodies/hooks.txt. regards Hugh On Saturday, Apr 5,

RE: (RADIATOR) AddToReply and Hosts

Thanks Hugh,,, unfortunately that makes things a bit more difficult for me... Is there anyway that I could use a variable created in a preclienthook from within a replyhook??? -Miko -Original Message- From: Hugh Irvine [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 5:13 PM To:

Re: (RADIATOR) Another feature suggestion: profiles via dynamic username lookup for AuthFILE

Hello Valentin - We have recently added an AuthenticateAttribute parameter which allows you to specify a different attribute to use other than User-Name, and we have also added generic caching of user database lookups. Perhaps you could check the latest Radiator 3.5 patches and let us know if