yeah its able to connect to open, captive portal, psk N/W without issue..
here is the output of tracebuf.
Auth Trace Buffer
-----------------
Feb 18 06:07:21 station-up * 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 - - wpa2 aes
Feb 18 06:07:21 eap-id-req <- 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 1 5
Feb 18 06:07:21 eap-start -> 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 - -
Feb 18 06:07:21 eap-id-req <- 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 1 5
Feb 18 06:07:21 station-down * 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 - -
Feb 18 06:07:32 station-up * 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 - - wpa2 aes
Feb 18 06:07:32 eap-id-req <- 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 1 5
Feb 18 06:07:32 eap-start -> 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 - -
Feb 18 06:07:32 eap-id-req <- 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 1 5
Feb 18 06:07:32 station-down * 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 - -
Feb 18 06:08:01 station-up * 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 - - wpa2 aes
Feb 18 06:08:01 eap-id-req <- 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 1 5
Feb 18 06:08:01 eap-start -> 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 - -
Feb 18 06:08:01 eap-id-req <- 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 1 5
Feb 18 06:08:01 station-down * 00:25:48:c0:1f:89
00:24:6c:b2:2d:c0 - -
--
sent from my android.
Thanks