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

markb · ‎2015-07-01

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 · ‎2015-07-07

Posted on July 07, 2015 at 15:45

Hi Jerry, thanks again for your swift reply. I am exploring changing the MiniAP ip address because I am trying to get UDP broadcast working when in MiniAP mode. If the module is in STA mode with an ip address of, say, 192.168.1.138 as handed out by the local DHCP server, I can broadcast UDP packets from the module to address 192.168.1.255 OK. But when the module is in MiniAP mode and it has the IP address of 172.31.12.1 then broadcasting to 172.31.12.255 does not give an error but the packets don't get delivered either.

So, the question is, what is the correct broadcast address to use when the IP address is 172.31.12.1 ? Or is there some other reason why UDP broadcasts fail when in MiniAP mode?

Cheers,

Mark

Gerardo GALLUCCI · ‎2015-07-07

Posted on July 07, 2015 at 15:55

# ip_ipaddr = 0.0.0.0
# ip_netmask = 0.0.0.0
# ip_gw = 0.0.0.0
# ip_dns = 0.0.0.0

into status/config are ok?

markb · ‎2015-07-07

Posted on July 07, 2015 at 16:08

The status output shows:

# ip_ipaddr = 172.31.12.1 # ip_netmask = 255.255.255.0 # ip_gw = 172.31.12.1 # ip_dns = 208.67.222.222

Gerardo GALLUCCI · ‎2015-07-07

Posted on July 07, 2015 at 17:16

Variables are ok.

I tried (a few months ago) in STA mode, but never in miniAP. I expect it should work, since IP addresses are delivered in the same way!

Give me some time to perform a couple of tests...

Sorry

jerry

Gerardo GALLUCCI · ‎2015-07-10

Posted on July 10, 2015 at 09:37

Tests confirmed your issue.

Opened a ticket for investigation/solving.

Sorry for this

jerry

markb · ‎2015-07-10

Posted on July 10, 2015 at 11:51

Hi Jerry,

Thanks for verifying that problem and raising a ticket.

Fortunately, it isn't critical for me but it would be nice if it works in the future.

Thanks again for your answers to my questions, I now have the module working well in my application.

Cheers,

Mark

valentin · ‎2017-01-26

Posted on January 26, 2017 at 23:38

Thanks from me for this info,

. I had pretty much the same issue, trying to join my WPA2 network.

Setting aut_type to 0 made it possible:

+WIND:2:Reset+WIND:1:Poweron (150410-c2e37a3-SPWF02S)+WIND:13:ST SPWF01SA2 IWM: Copyright (c) 2012-2014 STMicroelectronics, Inc. All rights Reserved.+WIND:3:Watchdog Running+WIND:46:WPA: Crunching PSK...+WIND:0:Console active+WIND:32:WiFi Hardware Started+WIND:21:WiFi Scanning+WIND:35:WiFi Scan Complete (0x0)+WIND:19:WiFi Join:xx:xx:xx:43:02:94+WIND:25:WiFi Association with '***_wireless' successful+WIND:51:WPA Handshake Complete+WIND:24:WiFi Up:x.x.1 �?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?

So my question now is: Your post below infers that setting auth_type to zero makes the module use WEP encryption? That cannot be the case because my wifi is definitely using WPA2 only - which seems to be confirmed by the WPA lines above.

If I set auth_type to 1, though, I get his output:

+WIND:2:Reset+WIND:1:Poweron (150410-c2e37a3-SPWF02S)+WIND:13:ST SPWF01SA2 IWM: Copyright (c) 2012-2014 STMicroelectronics, Inc. All rights Reserved.+WIND:3:Watchdog Running+WIND:0:Console active+WIND:32:WiFi Hardware Started+WIND:21:WiFi Scanning+WIND:35:WiFi Scan Complete (0x0)+WIND:19:WiFi Join:xx:xx:xx:xx:xx:xx+WIND:45:Dot11 AuthIllegal 1/2+WIND:75:Rejected Association (0xD) �?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?

The config producing the error:

# Dumping All Configuration Keys:# nv_manuf = ST# nv_model = SPWF01SA2# nv_serial = 2215P15051# nv_wifi_macaddr = 00:80:E1:B5:AF:25# 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 = 1# 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 = xx:xx:xx:xx:5F:77:69:72:65:6C:65:73:73:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00# wifi_ssid_len = 13# 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 = xxxxxxxxxxx# wifi_wpa_psk_text = xxxxxxxx# ip_use_dhcp = 1# ip_use_httpd = 1# ip_mtu = 1500# ip_hostname = xx# ip_apdomainname = xx.com# 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�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?

Can you explain, please? And is there a reference sheet available somewhere, detailing the error codes?

Thanks a lot!

Gerardo GALLUCCI · ‎2017-01-28

Posted on January 28, 2017 at 12:11

Hi,

using WPA/WPA2, wifi_auth_type must be set to 0. WPA does not support shared authentication.

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.

Ciao

jerry