SPWF01SA.11 connection to AP
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2015-07-27 5:03 AM
Posted on July 27, 2015 at 14:03The original post was too long to process during our migration. Please click on the attachment to read the original post.
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2015-07-27 5:21 AM
Posted on July 27, 2015 at 14:21
Hi,
Please update your FW.Are you sure your AP is set with WPA2 key? Scan command gives you ''WPA'', not ''WPA2''...RegardsjOptions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2015-07-27 5:41 AM
Posted on July 27, 2015 at 14:41
Hello Gerado,
yes, you are right Key is WPA not WPA2. Is there any difference, in AT Commands ? Or just FW upgrade will fix it ? Best regards, AlexOptions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2015-07-27 5:48 AM
Posted on July 27, 2015 at 14:48
I don't know if it fix the problem, but updating the FW we'll be able to get the deauthentication reason code after WIND:40.
It's a better starting point...jOptions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2015-07-27 6:44 AM
Posted on July 27, 2015 at 15:44
I've tested it now with an other Ap.
The module ony has problems with WPA. WPA2 is working fine Thanks for your help.