Re: caching mechanisms and clean disconnect

2006-11-17 Thread Josh Shamir
On 11/16/06, Alan DeKok [EMAIL PROTECTED] wrote: And what does the output of radiusd -X say? Is it rejecting the user? When I login with the same user (on the same machine), after a disconnection, if I want reconnect immediatly freeRADIUS receive the first request and it accept the user

Re: caching mechanisms and clean disconnect

2006-11-17 Thread Alan DeKok
Josh Shamir [EMAIL PROTECTED] wrote: When I login with the same user (on the same machine), after a disconnection, if I want reconnect immediatly freeRADIUS receive the first request and it accept the user (but the client isn't really connected to wifi network), Why not? after this,

caching mechanisms and clean disconnect

2006-11-16 Thread Josh Shamir
Hi, I've a problem regarding the clean disconnect of a client and some caching mechanisms. I briefly illustrate my problem : My system is composed by freeradius and chillispot with WPA enterprise (LDAP as backend). When i connect a client 1 to my system all works fine, except for the time taked

Re: caching mechanisms and clean disconnect

2006-11-16 Thread Alan DeKok
Josh Shamir [EMAIL PROTECTED] wrote: When i connect a client 1 to my system all works fine, except for the time taked by authentication process, i'm using WinXP SP2 build-in supplicant. (How I can speed up this procedure?Could you suggest me some opensource supplicant?) SecureW2 is one, but