"Josh Shamir" <josh.shamir@gmail.com> 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 I don't know if it will help.
The problem is that when I disconnect client 1 from my system (just connecting my client to another network) and then i reconnect client1 to the system the WPA authentication failed for about 10 minutes.After this time authentication of client 1 works fine.
And what does the output of "radiusd -X" say? Is it rejecting the user?
So I think that this fact is caused by some cache mechanism used by freeradius.
No.
How can I make sure that a Client is disconnected in clean way and remove his session after it has disconnected inside Freeradius?
You don't. FreeRADIUS doesn't cache sessions that way. Old sessions don't affect new sessions unless you configure it that way. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog