What does +WIND:54:Dot11 AuthIllegal 0/2 signify?

[markb]

Posted on July 01, 2015 at 10:00 Hi, I am getting the above error indication when trying to access an AP, what does it mean? Cheers, Mark

[markb]

Posted on July 03, 2015 at 11:12

OK, thanks but I gave up waiting and managed to read the flash from another module so my test module is up and running again. But I still have the original problem which is when it tries to associate with an AP it fails with:

+WIND:45:Dot11 AuthIllegal 0/2 +WIND:75:Rejected Association (0xD) I am using WPA/WPA2 and the text key is getting crunched. The AP is a TP-LINK TL-WA701N and works with all other WIFI devices I have. Could you give any more info about what is wrong here? Thanks

[Gerardo GALLUCCI]

Posted on July 03, 2015 at 11:27

Please share AT&V dump

[markb]

Posted on July 03, 2015 at 11:41

# Dumping All Configuration Keys:
# nv_manuf = ST
# nv_model = SPWF01SA1
# nv_serial = 2914D13607
# nv_wifi_macaddr = 00:80:E1:FF:D2:0C
# blink_led = 0
# wind_off_low = 0x00000000
# wind_off_medium = 0x00000000
# wind_off_high = 0x00000000
# user_desc = anonymous
# escape_seq = at+s.
# localecho1 = 0
# console1_speed = 115200
# console1_hwfc = 0
# console1_enabled = 1
# sleep_enabled = 0
# standby_enabled = 0
# standby_time = 10
# wifi_tx_msdu_lifetime = 0
# wifi_rx_msdu_lifetime = 0
# wifi_operational_mode = 0x00000011
# wifi_beacon_wakeup = 1
# wifi_beacon_interval = 100
# wifi_listen_interval = 0
# wifi_rts_threshold = 3000
# wifi_ssid = 43:4C:46:32:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
# wifi_ssid_len = 4
# wifi_txfail_thresh = 5
# wifi_ht_mode = 0
# wifi_channelnum = 6
# wifi_opr_rate_mask = 0x00003FCF
# wifi_bas_rate_mask = 0x0000000F
# wifi_mode = 1
# wifi_auth_type = 1
# wifi_atim_window = 0
# wifi_powersave = 0
# wifi_tx_power = 18
# wifi_rssi_thresh = 0
# wifi_rssi_hyst = 0
# wifi_ap_idle_timeout = 120
# wifi_beacon_loss_thresh = 10
# wifi_priv_mode = 2
# wifi_wep_keys[0] = 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
# wifi_wep_keys[1] = 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
# wifi_wep_keys[2] = 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
# wifi_wep_keys[3] = 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
# wifi_wep_key_lens = 00:00:00:00
# wifi_wep_default_key = 0
# wifi_wpa_psk_raw = 0A:C9:1E:70:69:21:CE:16:3D:D4:F9:AE:DE:96:95:05:6D:B6:30:06:53:CF:47:6C:9A:C7:F0:A8:F3:D1:FB:73
# wifi_wpa_psk_text = plasmagun
# ip_use_dhcp = 1
# ip_use_httpd = 1
# ip_mtu = 1500
# ip_hostname = iwm-FF-D2-0C
# ip_apdomainname = captiveportal.net
# ip_apredirect = firstset.html
# ip_ipaddr = 0.50
# ip_netmask = 0
# ip_gw = 0.1
# ip_dns = 0.1
# ip_http_get_recv_timeout = 3000
# ip_wait_timeout = 12000
# ip_dhcp_timeout = 20
# ip_sockd_timeout = 250

# Status & Statistics:
# version = 150410-c2e37a3-SPWF01S
# reset_reason = 2
# conf_flag = 5
# system_uptime = 799
# system_sleeptime = 0
# gpio_enable = 0
# captiveportal = 0
# wifi_state = 7
# wifi_bssid = 74:EA:3A:BA:89:67
# wifi_aid = 0
# wifi_channelnum = 5
# wifi_sup_rate_mask = 0x003FFFCF
# wifi_bas_rate_mask = 0x0000000F
# wifi_chan_activity2 = 0x00000000
# wifi_max_tx_power = 18
# wifi_gf_mode = 0
# wifi_reg_country =
# wifi_dtim_period = 1
# wifi_sleeping = 0
# wifi_num_assoc = 0
# ip_ipaddr = 0.0.0.0
# ip_netmask = 0.0.0.0
# ip_gw = 0.0.0.0
# ip_dns = 0.0.0.0
# ip_sock_open = 0
# ip_sockd_port = 0
# free_heap = 20992
# min_heap = 20848
# current_time = 3615

[Gerardo GALLUCCI]

Posted on July 03, 2015 at 12:21

I saw TL-WA701N is an N (B/G compatible) Access Point.

Module, on the other hand, is configured as B/G only.I don't know where is the problem, and I have no that AP.Try this way:- at+s.scfg=

wifi_ht_mode,1

- at+s.scfg=wifi_opr_rate_mask,

0x3FFCF

- at&w- reboot (SW or HW)Helps?

[markb]

Posted on July 07, 2015 at 09:06 Hi, sorry for the slow reply, I have been busy chasing other problems. No, it didn't help. If I turn off the security for that AP, the module will connect to it happily so I think it must be a security related problem. Any other suggestions? Also, what does that error message actually say? What's the 0/2 mean? Thanks, Mark

[Gerardo GALLUCCI]

Posted on July 07, 2015 at 10:15

Problem is that AP doesn't like authentication type requested by module.

0 refers to authentication alghorithm received from AP.OPEN   is 0; SHARED is 1.Module receives 0, while configuration variable is set to 1.2 refers to ''challenge'' steps  received from AP.Big info is taken from next WIND:75. 0x0D, 13, Means: ''

Responding station does not support the specified authentication algorithm

''Double check: are you sure your AP is configured in WPA? It seems that it's configured in WEP mode (open/shared mismatch means something only in WEP mode).Try to set wifi_auth_type = 0 on module. What does it happen?Can you share a sniff? Use wireshark, for example.Thanksjerry

[markb]

Posted on July 07, 2015 at 10:47 Yes, setting wifi_auth_type to 0 makes it work. It can now associate and data flows. I have tried with two access points (one a Netgear and the other a TP-LINK) and with wifi_auth_type set to 0 it can talk to either when the AP security is WPA/WPA2 but if wifi_auth_type is set to 1 it fails for both APs - the TP-LINK fails as we have previously discussed and the Netgear fails because it gets no further than WIND:19 and just keeps retrying. So, what magic does setting wifi_auth_type to 0 do and will that work with other APs? Mark

[Gerardo GALLUCCI]

Posted on July 07, 2015 at 11:21

Hi Mark,

From Google:Open System and Shared Key

The Open System and Shared Key authentication methods use WEP encryption. WEP is not as secure as WPA2 and WPA (Wi-Fi Protected Access). We recommend you do not use these less secure methods unless your wireless clients do not support WPA or WPA2.

• Open System â€�? Open System authentication allows any user to authenticate to the access point. This method can be used with no encryption or with WEP encryption.
• Shared Key â€�? In Shared Key authentication, only those wireless clients that have the shared key can connect. Shared Key authentication can be used only with WEP encryption.

The last sentence is clear: ''

Shared Key authentication can be used only with WEP encryption

''.AP gives a status error (0x0D), and module aborts the authentication process at the beginning.I'll give this feedback to the right people for updating User Manuals, and highlight that WPA+SharedAuth=Rejection!Thanks for your feedback.Ciaojerry

[markb]

Posted on July 07, 2015 at 14:18 Hi Jerry, Thanks for all your help, it's working pretty well now. One other question (there's always another question!) How do you specify the IP address to be used when you force AP mode via the GPIO signal? At the moment, it is 172.31.12.1 but I would like to change that if possible. Cheers, Mark

[Gerardo GALLUCCI]

Posted on July 07, 2015 at 14:32

Use variable ip_use_dhcp.

Default, 172.31.12.1 when ip_use_dhcp is 1, is self-generated, based on MAC address.Set ip_use_dhcp to 2, for custom address, based on ip_ipaddr & Co. variables.0=off (in STA mode: the variables ip_ipaddr, ip_netmask and ip_gw must be properly set to connect to the AP),1=on (in STA mode: the ipaddr, netmask and gw will be provided by the AP),2=on&customize (in MiniAP mode: user can customize the ip_ipaddr of the MiniAP, the ip_address of the client is automatically assigned by the MiniAP)