Why are users kicked off the network before PSK expires?

[lachlan_hughes]

I have a problem with patrons needing to re-enter passwords to gain access to the network but they are being told a new PSK is required.

I have a ruckus ZD1106 (version: 9.6.1.0 build 15) with a mesh of about 6 APs.

The Dynamic-PSK Expiration is set to Unlimited, but it would seem clients are being denied access before the provided PSK grace period has ended. (excuse me if my terminology is around the wrong way)

The following user informed staff that they were kicked off the network about 2013/12/19 19:45. But to me this scrapping does not seem to tell me why. Initially the user was unnameed (MAC Address) but was given a second PSK and named room 6.

--------------------------------------------------------------------------------

2013/12/19 22:25:19 Low room 6 User[room 6] leave WLAN[Hotel WiFi] at AP[Upstairs Corridor] with Session Time[9398.02 sec] RX Bytes[45307717] TX Bytes[1220432835]
2013/12/19 22:25:19 Low room 6 User[room 6] disconnects from WLAN[Hotel WiFi] at AP[Upstairs Corridor]
2013/12/19 19:49:14 Low room 6 User[room 6] of WLAN[Hotel WiFi] is authorized at AP[Upstairs Corridor]
2013/12/19 19:49:10 Low room 6 User[room 6] from [10.0.1.159] approved for guest access (guest pass was generated by [Reception])
2013/12/19 19:48:41 Low User[34:c0:59:5c:xx:xx] joins WLAN[Hotel WiFi] from AP[Upstairs Corridor]
2013/12/19 19:45:46 Low User[34:c0:59:5c:xx:xx] leave WLAN[Hotel WiFi] at AP[Upstairs Corridor] with Session Time[122.22 sec] RX Bytes[28306] TX Bytes[113036]
2013/12/19 19:45:46 Low User[34:c0:59:5c:xx:xx] disconnects from WLAN[Hotel WiFi] at AP[Upstairs Corridor]
2013/12/19 19:43:43 Low User[34:c0:59:5c:xx:xx] joins WLAN[Hotel WiFi] from AP[Upstairs Corridor]

--------------------------------------------------------------------------------

Is there a setting somewhere that would cause a MAC address to be restricted or kicked if they left the network for too long (eg turned off device or left physical network)?

Any help will be appreciated.

[martin_kane]

I remember this happening when we first started, but can't remember exactly what simple thing we did to fix it! Try turning off "Enable captive portal/Web authentication" on the network you ultimately want the users' DPSKs to be working on. I suspect we then had 2 WLANS set up - one as described above and another which issued the DPSKs for that WLAN.

I wonder initially if we were trying to distribute AND run DPSKs off the same WLAN?

Oh dear, it was two years ago and my memory is so bad....