https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Windows-IAS-for-802-1x-log-warnings/m-p/14353#M3615 Hi, <BR /><BR /> Currently I'm running my standalone AP ZF 7982 9.8.1.0.101 against Microsoft IAS (2008R2). <BR /> From client side everything is okay. Also from server side. But only what bothers me is that warning. <BR /> 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. <BR /> II can confirm that this problem/behaviour has a long history. At least I can remember for version 9.6 throws also this warning. Mon, 24 Nov 2014 08:51:57 GMT sven_jaanson 2014-11-24T08:51:57Z https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Windows-IAS-for-802-1x-log-warnings/m-p/14351#M3613 Hi, <BR /><BR /> What should I do with the following warning on Standalone ZF7982 AP?: <BR /><BR /> Nov 22 15:34:08 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.11: associated <BR /> 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 <BR /> 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 <BR /> 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 <BR /> 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 <BR /> 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 <BR /> 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 <BR /> Nov 22 15:34:10 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee WPA: pairwise key handshake completed (RSN) <BR /> Nov 22 15:34:10 RuckusAP8K daemon.info hostapd: wlan1: STA 00:24:d6:9a:04:ee IEEE 802.1X: authenticated <BR /><BR /> I configured connection request policy in IAS that session-timeout should be 150 <BR /> (Added Standard RADIUS Attribute (27) session-timeout to 150) but nothing changes.. Sat, 22 Nov 2014 15:38:08 GMT https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Windows-IAS-for-802-1x-log-warnings/m-p/14351#M3613 sven_jaanson 2014-11-22T15:38:08Z https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Windows-IAS-for-802-1x-log-warnings/m-p/14352#M3614 can you explain a bit more about your config so we can check further. <BR /><BR /> what version are you running into the AP ? Sun, 23 Nov 2014 12:16:47 GMT https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Windows-IAS-for-802-1x-log-warnings/m-p/14352#M3614 martin_martin 2014-11-23T12:16:47Z https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Windows-IAS-for-802-1x-log-warnings/m-p/14353#M3615 Hi, <BR /><BR /> Currently I'm running my standalone AP ZF 7982 9.8.1.0.101 against Microsoft IAS (2008R2). <BR /> From client side everything is okay. Also from server side. But only what bothers me is that warning. <BR /> 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. <BR /> II can confirm that this problem/behaviour has a long history. At least I can remember for version 9.6 throws also this warning. Mon, 24 Nov 2014 08:51:57 GMT https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Windows-IAS-for-802-1x-log-warnings/m-p/14353#M3615 sven_jaanson 2014-11-24T08:51:57Z