Why do SZ shows us "Client session expired"?

hyosang_choi — Mon, 10 Sep 2018 00:47:06 GMT

Hi.

Sometimes we find event log as "Client session expired" on web-ui of SZ100 .

A security type of the SSID is wpa2-psk-aes.

I know that type of psk don't have session-timeout.

Why do SZ show us the message?

Regards.

Re: Why do SZ shows us "Client session expired"?

michael_brado — Tue, 11 Sep 2018 20:46:38 GMT

Was it from an AP that the client has roamed away from?

Re: Why do SZ shows us "Client session expired"?

hyosang_choi — Wed, 12 Sep 2018 01:21:14 GMT

The log is shown regardless of roaming.

Duration is exacty 2days.

Re: Why do SZ shows us "Client session expired"?

michael_brado — Wed, 12 Sep 2018 16:02:37 GMT

Has anyone reported any kind of problem? 2 days sounds like a lengthy session timeout set on the WLAN.

Re: Why do SZ shows us "Client session expired"?

hyosang_choi — Thu, 13 Sep 2018 04:58:20 GMT

It's odd.

Recently In hospitality some customer deployed IOT device.

The devices is connecting 365days to WIFI.

Sometimes, after the device is disconnected by the deauth as "session expired" , don't connect to wifi again.

I also know though it's disconnected, the device have to re-conntected to WIFI automatically.

But this timeout is very odd because wlan type is open or psk not wispr having session timeout.

See below, the device is connected to WIFI very normally.

Session duration is exactly 2days.

Wlan type is open and no encryption.

In this case the AP should not have session-timeout.

See below log.

We can find "deauthenticated due to session timeout".

And duration is about "172800 sec" exactly "sessionDuration"="172803".

Sep 13 03:46:22 Hospitality-AP local1.info sessionMgr[554]: handle_scg_del_ue_ctx_req:1074 UE[5c:cf:7f:cc:0f:8d][wlan7]msg->msg.apDelCtxtReq.sessTerCause=3
Sep 13 03:46:22 Hospitality-AP daemon.info hostapd: wlan7: STA 5c:cf:7f:cc:0f:8d IEEE 802.11: wlan7: IEEE 802.11: ***DEBUG*** deauthenticated due to session timeout
Sep 13 03:46:22 Hospitality-AP daemon.info hostapd: @@208,clientSessionExpiration,"apMac"="xx:xx:xx:xx:xx:xx","clientMac"="5c:cf:7f:cc:0f:8d","ssid"="WLAN-open","bssid"="xx:xx:xx:xx:xx:xx","userId"="","wlanId"="12","iface"="wlan7","tenantUUID"="839f87c6-d116-497e-afce-aa8157abd30c","apName"="Hospitality-AP","clientIP"="10.0.4.31","vlanId"="3002","radio"="b/g/n","encryption"="None","hostname"="HomeMate_device","firstAuth"="1536637579","associationTime"="0","ipAssignTime"="1536637582","disconnectTime"="1536810382","sessionDuration"="172803","disconnectReason"="2","rxFrames"="3579","rxBytes"="493624","txFrames"="165603","txBytes"="8626471","peakRx"="48252","peakTx"="14504","rssi"="63","receivedSignalStrength"="-42"
Sep 13 03:46:22 Hospitality-AP daemon.info hostapd: wlan7: STA 5c:cf:7f:cc:0f:8d IEEE 802.11: wlan7: IEEE 802.11: hostapd_stats_upd_client, username=, disconReason=2
Sep 13 03:46:22 Hospitality-AP daemon.info hostapd: IEEE 802.11: hostapd_stats_send2collectd, send data len=216
Sep 13 03:46:22 Hospitality-AP daemon.err collectd[4119]: client_upd_handler, receive updSta data with len 216
Sep 13 03:46:22 Hospitality-AP local1.err sessionMgr[554]: sm_handle_ipc_ue_context_update:417 No UE context found
Sep 13 03:46:22 Hospitality-AP local1.info sessionMgr[554]: handle_ue_state_change:380 UE[5c:cf:7f:cc:0f:8d][wlan7]UE state changed from [uninitialized] to [deauth]
Sep 13 03:46:22 Hospitality-AP daemon.warn Eved: STA-DISASSOC-REASON [domlme(),7144,domlme] 5c:cf:7f:cc:0f:8d rx_rssi=47,ack_rssi=0,reason=2,freq=2412,chan=1,rx pkt,byte;tx pkt,byte=(3579,493624,165603,8626471)
Sep 13 03:46:22 Hospitality-AP daemon.info hostapd: wlan7: STA 5c:cf:7f:cc:0f:8d IEEE 802.11: wlan7: IEEE 802.11: disassociated

Also see below log. That's a log after reconntected.

There is no time-out such as "sessionTimeout=0".

Sep 13 03:46:26 Hospitality-AP local1.info sessionMgr[554]: handle_ue_state_change:380 UE[5c:cf:7f:cc:0f:8d][wlan7]UE state changed from [uninitialized] to [session_active]
Sep 13 03:46:26 Hospitality-AP local1.info sessionMgr[554]: build_and_send_scg_ue_ctx_create:490 UE[5c:cf:7f:cc:0f:8d][wlan7]apCrtCtxtReq.ueCtxtState=1 dot11State=1 wlanid=12 sessStartTime=1536810383 vlan=3002 sessionTimeout=0

The device will be diconnected to WIFI after 2 day.

Does anyone know why this works?

Regards.

Re: Why do SZ shows us "Client session expired"?

hyosang_choi — Wed, 19 Sep 2018 07:49:01 GMT

Has anyone seen symptoms?

Re: Why do SZ shows us "Client session expired"?

ja_moreno — Thu, 20 Sep 2018 08:27:45 GMT

Hello,

This behavior is as per design. For Open WLAN where no Session timeout is configurable, there is an internal timeout of 48 hours since release 3.4.

Regards.

Re: Why do SZ shows us "Client session expired"?

hyosang_choi — Mon, 05 Nov 2018 09:03:03 GMT

Thanks for reply.

topic Re: Why do SZ shows us "Client session expired"? in SmartZone and Virtual SmartZone

Why do SZ shows us "Client session expired"?

Re: Why do SZ shows us "Client session expired"?

Re: Why do SZ shows us "Client session expired"?

Re: Why do SZ shows us "Client session expired"?

Re: Why do SZ shows us "Client session expired"?

Re: Why do SZ shows us "Client session expired"?

Re: Why do SZ shows us "Client session expired"?

Re: Why do SZ shows us "Client session expired"?