ZF 7372 and Sony M4 aqua lollipop is unable to connect

[bart_omiej_wiec]

Hi, ZF 7372 standalone 100.1.0.0.194, two ssids one 2.4, one 5 Ghz and Sony M4 aqua lollipop is unable to connect, all other devices connects normal (android phones, ipad, iphone, tablet, pc etc). Any suggestions?

[monnat_systems]

Bartłomiej Świech
Just for testing i would suggest as following:

You create a new WLAN which is open and check if sony device is working or not.
You create a new WLAN which is WPA/PSK and TKIP/AUTO -- check if sony device is working or not.
You create a new WLAN which is WPA2/PSK and TKIP/AES/AUTO -- check if sony device is working or not.

compare the above configuration with your current one so that you don't try the same thing which you already know. Also if you find a working configuration, apply it to your current one.
please note that this will interuppt your current users for a quick/short duration.

[supmang]

I have the same issue.

I recently updated my phone to Android 5.0 (lollipop) and then 5.1.1 and neither version is able to connect to my R500 with WPA2 AES. The R500 is also on version 100.1.0.0.194.

I tried creating a temporary SSID with WEP and it can connect to that one without issue. I can also connect to wifi at the office (Cisco hardware) and an older Netgear N router running dd-wrt.

All other devices connect to the R500 without issue. I only have a problem with Android 5+.

I found this Android bug report, although it's unclear whether the actual bug lies in the Android code or AP firmware code: https://code.google.com/p/android/issues/detail?id=78702

I also ran across this Cisco support post, which points the finger at PMF (or MFP?) and may or may not be directly related. https://supportforums.cisco.com/discussion/12543141/wap371-firmware-v1202-wireless-client-incompatib...

[monnat_systems]

suggest that you try connecting and capture the AP support log to see what it is reporting for all that disconnections...

do you see same issue if you downgrade the AP to 9.8.2 or 9.8.3?

[supmang]

This is what I get in the AP logs. I haven't had a chance to downgrade the firmware yet.

Aug 25 03:40:31 RuckusAP daemon.info hostapd: wlan1: STA IEEE 802.11: associated
Aug 25 03:40:31 RuckusAP daemon.info hostapd: wlan1: STA WPA: pairwise key handshake completed (RSN)
Aug 25 03:40:35 RuckusAP daemon.info hostapd: wlan1: STA IEEE 802.11: disassociated
Aug 25 03:40:35 RuckusAP daemon.info hostapd: wlan1: STA IEEE 802.11: unknown reason code= 2
Aug 25 03:40:35 RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=,func=ieee80211_send_mgmt,line=4492,hint=send station disassociate,rx_rssi=36,ack_rssi=0,reason=2,freq=2417,chan=2,stats=(0,0,0,0)
Aug 25 03:40:38 RuckusAP daemon.info hostapd: wlan1: STA IEEE 802.11: associated
Aug 25 03:40:38 RuckusAP daemon.info hostapd: wlan1: STA WPA: pairwise key handshake completed (RSN)
Aug 25 03:40:42 RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=,func=ieee80211_send_mgmt,line=4492,hint=send station disassociate,rx_rssi=34,ack_rssi=0,reason=2,freq=2417,chan=2,stats=(0,0,0,0)
Aug 25 03:40:42 RuckusAP daemon.info hostapd: wlan1: STA IEEE 802.11: disassociated
Aug 25 03:40:42 RuckusAP daemon.info hostapd: wlan1: STA IEEE 802.11: unknown reason code= 2
Aug 25 03:40:45 RuckusAP daemon.info hostapd: wlan1: STA IEEE 802.11: associated
Aug 25 03:40:45 RuckusAP daemon.info hostapd: wlan1: STA WPA: pairwise key handshake completed (RSN)
Aug 25 03:41:00 RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=,func=ieee80211_send_mgmt,line=4492,hint=send station disassociate,rx_rssi=39,ack_rssi=0,reason=2,freq=2417,chan=2,stats=(0,0,0,0)
Aug 25 03:41:00 RuckusAP daemon.info hostapd: wlan1: STA IEEE 802.11: disassociated
Aug 25 03:41:00 RuckusAP daemon.info hostapd: wlan1: STA IEEE 802.11: unknown reason code= 2