Skip to content
This repository has been archived by the owner on Mar 15, 2019. It is now read-only.

Could not connect to AP #12

Open
mdumouchel opened this issue Mar 1, 2015 · 6 comments
Open

Could not connect to AP #12

mdumouchel opened this issue Mar 1, 2015 · 6 comments

Comments

@mdumouchel
Copy link

Error: Could not connect to AP
Error: Could not obtain connection details

Is there any documentation on this message, or way I could trouble shoot why I keep getting this message? I am running the example connection test, I updated the ssid and password to values that should work. The only one I'm a bit lost on is

unsigned int ap_security = WLAN_SEC_WPA2;  

What other options are available for this? On my windows machine it is WPA2-personal, and encryption type of AES. Not sure if these are important.

@ShawnHymel
Copy link
Contributor

WLAN_SEC_WPA2 is correct, as you are using WPA2 encryption with your WiFi network. However, the library does not support AES encryption, which is used to communicate the WiFi password. You will either need to turn off AES on your router or try a different library (I've seen ones that supports AES).

@mdumouchel
Copy link
Author

Curious is there a reason why AES is not supported? Is it something we could include with a pull request or is not that trivial?

@ShawnHymel
Copy link
Contributor

It could be done in a pull request, but I found that 1) it was not trivial to implement (as it had to be done all in software - the CC3000 doesn't do it, the microcontroller does) and 2) it took up vast amounts of resources such that microcontrollers with few resources (e.g. ATmega 328p) would be just about out of space when you included AES.

@mdumouchel
Copy link
Author

So what is the base encryption set to in the example code? I'm looking to setup a router just to get this running what specs/configuration should I have to make this work? Just want to get this working before I start messing with stuff.

Thanks for all the help and information so far!

@ShawnHymel
Copy link
Contributor

There is no encryption for the connection process - it's all done in the clear. Once you have made a connecton to the AP, communication is done with WPA2.

@ShawnHymel
Copy link
Contributor

I take back my previous comment - someone correctly pointed out that WPA2 requires AES to connect. As far as I know, the CC3000 does encrypt the SSID and password when it transmits. However, I had it confused with the SmartConfig process, which does not support AES (at least in the library right now). Apologies!

If you're going through the process of setting up another router to test the CC3000, you may want to try it without any encrpytion (e.g. no WPA or WEP) to see if it works. You will need to change ap_security to WLAN_SEC_UNSEC.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants