caching mechanisms and clean disconnect
- To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org>
- Subject: caching mechanisms and clean disconnect
- From: "Josh Shamir" <josh.shamir@gmail.com>
- Date: Thu, 16 Nov 2006 10:03:26 +0100
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=sIqR1W0j+ctvzDZr+gGfK8IVfscw3DZB4AMNi9qr49KzW25Fd89opNewZCV0bIjSr2sjZzpIT9zW7OO75KlF0YYcp0LRuvnjCVPN5zUZi6TJqsr1QuS4Kz+mOEjiG9jaDpwag5cV3BSZP1y3s2CUj9SFSkQd2BU1CKH9ZJK0D8Q=
- Reply-to: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>
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 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?)
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.
So I think that this fact is caused by some cache mechanism used by freeradius.
How can I make sure that a Client is disconnected in clean way and remove his session after it has disconnected inside Freeradius?
Thanks for attention
Regards, Josh
This archive was generated by a fusion of
Pipermail (Mailman edition) and
MHonArc.