Re: [RADIATOR] radiator Timeout handling

2011-04-06 Thread David Zych
On 4/6/2011 4:26 PM, Heikki Vatiainen wrote: > On 04/06/2011 10:22 PM, David Zych wrote: >> I just ran into this same problem; my DB got into a state where >> DBI->connect was working fine but actual INSERTs were timing out, and >> the non-observance of FailureBackoffTime in this situation resulted

Re: [RADIATOR] Windows Server 2008 R2

2011-04-06 Thread Heikki Vatiainen
On 04/06/2011 05:09 PM, Remco van Noorloos wrote: > We are planning to install Radiator on a Windows Server 2008 R2 > server. I checked the reference manual but only Windows Server 2003 > is mentioned as supported. Is Windows Server 2008 supported or should > I use a Windows 2003 server? I have m

Re: [RADIATOR] Password Retry / Password Change For TTLS MsChapV2

2011-04-06 Thread Heikki Vatiainen
On 04/06/2011 07:33 PM, Aman Arneja wrote: > I am trying to find out if radiator supports Password Retry and Password > Change scenarios ( For expired password) with TTLS Mschapv2 ( as Non Eap > Method) If so can some1 please guide me as to how to configure the server > for these options? If not

Re: [RADIATOR] AuthBy LDAP2, HoldServerConnection and missing Retry parameter

2011-04-06 Thread Heikki Vatiainen
On 04/06/2011 03:39 PM, Christian Kratzer wrote: >> Wed Apr 6 00:32:34 2011: ERR: ldap search for (|(mail=foo)(uid=bar)) failed >> with error LDAP_SERVER_DOWN. >> Wed Apr 6 00:32:34 2011: ERR: Disconnecting from LDAP server (server >> foo.uni-ulm.de:636). >> Wed Apr 6 00:32:34 2011: DEBUG: Au

[RADIATOR] Password Retry / Password Change For TTLS MsChapV2

2011-04-06 Thread Aman Arneja
changing subject On Wed, Apr 6, 2011 at 10:03 PM, Aman Arneja wrote: > Hi Team > > I am trying to find out if radiator supports Password Retry and Password > Change scenarios ( For expired password) with TTLS Mschapv2 ( as Non Eap > Method) If so can some1 please guide me as to how to configure

Re: [RADIATOR] radiator Timeout handling

2011-04-06 Thread Heikki Vatiainen
On 04/06/2011 10:22 PM, David Zych wrote: David, thanks for the suggestion and comments. Please see my comments below: > I just ran into this same problem; my DB got into a state where > DBI->connect was working fine but actual INSERTs were timing out, and > the non-observance of FailureBackoffT

Re: [RADIATOR] radiator Timeout handling

2011-04-06 Thread David Zych
On 9/20/2010 12:00 PM, Michael wrote: >> > I'm having a couple issues with. Maybe it would be >> > considered a bug i'm not sure. >> > >> > 1. the Timeout handling. >> > >> > >>> >> From my testing, it a

[RADIATOR] Password Retry / Password Change For TTLS MsChapV2

2011-04-06 Thread Aman Arneja
Hi Team I am trying to find out if radiator supports Password Retry and Password Change scenarios ( For expired password) with TTLS Mschapv2 ( as Non Eap Method) If so can some1 please guide me as to how to configure the server for these options? If not what would be the easiest method to add sup

[RADIATOR] Windows Server 2008 R2

2011-04-06 Thread Remco van Noorloos
Dear all, We are planning to install Radiator on a Windows Server 2008 R2 server. I checked the reference manual but only Windows Server 2003 is mentioned as supported. Is Windows Server 2008 supported or should I use a Windows 2003 server? Thanks, PROXSYS* Remco van Noorloos

Re: [RADIATOR] AuthBy LDAP2, HoldServerConnection and missing Retry parameter

2011-04-06 Thread Christian Kratzer
Hi, On Wed, 6 Apr 2011, Karl Gaissmaier wrote: > Hi RADIATOR team, > > I've got a problem with Version 4.7 and AuthBy LDAP2. The LDAP server > terminates > the connection after 10min of client idle as configured in slapd.conf. > > Seems that the RADIATOR doesn't recognize this, and the first ACC

[RADIATOR] AuthBy LDAP2, HoldServerConnection and missing Retry parameter

2011-04-06 Thread Karl Gaissmaier
Hi RADIATOR team, I've got a problem with Version 4.7 and AuthBy LDAP2. The LDAP server terminates the connection after 10min of client idle as configured in slapd.conf. Seems that the RADIATOR doesn't recognize this, and the first ACCESS-REQUEST after this termination gets the following error: