Windows IAS for 802.1x log warnings

[sven_jaanson]

Hi,

What should I do with the following warning on Standalone ZF7982 AP?:

Nov 22 15:34:08 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.11: associated
Nov 22 15:34:08 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.1X: ignored too small Session-Timeout 30, override as 120
Nov 22 15:34:09 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.1X: ignored too small Session-Timeout 30, override as 120
Nov 22 15:34:09 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.1X: ignored too small Session-Timeout 30, override as 120
Nov 22 15:34:09 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.1X: ignored too small Session-Timeout 30, override as 120
Nov 22 15:34:09 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.1X: ignored too small Session-Timeout 30, override as 120
Nov 22 15:34:09 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.1X: ignored too small Session-Timeout 30, override as 120
Nov 22 15:34:10 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee WPA: pairwise key handshake completed (RSN)
Nov 22 15:34:10 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.1X: authenticated

I configured connection request policy in IAS that session-timeout should be 150
(Added Standard RADIUS Attribute (27) session-timeout to 150) but nothing changes..

[martin_martin]

can you explain a bit more about your config so we can check further.

what version are you running into the AP ?

[sven_jaanson]

Hi,

Currently I'm running my standalone AP ZF 7982 9.8.1.0.101 against Microsoft IAS (2008R2).
From client side everything is okay. Also from server side. But only what bothers me is that warning.
Basically my laptopts authenticate as a computer against IAS using certificates. But mentioned session-timeout attribute in IAS Connection request policy has no viable effect on ruckus AP side.
II can confirm that this problem/behaviour has a long history. At least I can remember for version 9.6 throws also this warning.