Thanks for your reply. 

This is what I see for martin, you can see every 1 or 2 minutes, radius server is getting auth request

Sep 24 11:47:04 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7 via TLS tunnel)
Sep 24 11:47:04 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7)
Sep 24 11:47:06 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7 via TLS tunnel)
Sep 24 11:47:06 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7)
Sep 24 11:47:28 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7 via TLS tunnel)
Sep 24 11:47:28 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7)
Sep 24 11:47:35 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7 via TLS tunnel)
Sep 24 11:47:35 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7)
Sep 24 11:48:10 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7 via TLS tunnel)
Sep 24 11:48:10 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7)
Sep 24 11:48:14 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7 via TLS tunnel)
Sep 24 11:52:21 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7 via TLS tunnel)
Sep 24 11:52:21 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7)
Sep 24 11:57:48 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7 via TLS tunnel)
Sep 24 11:57:49 radiusfront1 radiusd[28569]: Login OK: [martin] (from client acesspoint13 port 0 cli 97-d5-c7-8e-06-g7)

On Fri, Sep 26, 2014 at 11:52 AM, Alan DeKok <aland@deployingradius.com> wrote:
Rando Nakarmi wrote:
> For example, my phone got connected - authenticated, then i locked the
> phone, after a while  I open the phone, when it re-scan the network it
> actually sends the authentication request- gets re-authenticated.

  That's how it works.  The phone disconnects from the access point in
order to save battery life.  Since it's disconnected, when it goes back
online, it has to re-connect and re-authenticate.

> Is there a way, it only authenticates once, if you are in same wireless
> access point ? I meant, when device re-scans the network and if you are
> with the same Wireless access point not to send the auth request to the
> server over and and over ?

  You can use session caching.  See the "cache" subsection of the "eap"
module.  It will make later authentications faster.  But it won't stop
them from coming.

  In this case, the WiFi phone is asking for re-authentication, and the
NAS is requiring re-authentication.  RADIUS is just receiving the
authentication requests, and processing them.

  Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html