caching mechanisms and clean disconnect
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
"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
On 11/16/06, Alan DeKok <aland@deployingradius.com> 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 (but the client isn't really connected to wifi network), after this, FreeRADIUS do nothing for some second (abount two minutes) and after this idle time, the authentication restart and the client is connected. When I login with another use (on the same machine), after a disconnection, if I want reconnect immedialty FreeRADIUS does not receive nothing, At this point, I think that it's a client problem, but my question is: why there is this idle time? Regards
"Josh Shamir" <josh.shamir@gmail.com> 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, FreeRADIUS do nothing for some second (abount two minutes) and after this idle time, the authentication restart and the client is connected.
Well, yes. If the client isn't asking to be connected, FreeRADIUS does nothing.
When I login with another use (on the same machine), after a disconnection, if I want reconnect immedialty FreeRADIUS does not receive nothing, At this point, I think that it's a client problem, but my question is: why there is this idle time?
You answered your own question: It's a client problem. No amount of poking FreeRADIUS will make the client reconnect immediately. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (2)
-
Alan DeKok -
Josh Shamir