cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Wi-Fi Combo

New Contributor II

nsankar​ or vik86

Do either of you have a working example of the join_ent command from the test.console app?

I get the following error after compiling in a known good key and certificate.

> join_ent sw-rnd3 eap_tls <user name> <password> wpa2

Joining : sw-rnd3

Supplicant received link event

Supplicant error 6011

Failed to join : sw-rnd3

Joining : sw-rnd3

Failed to join : sw-rnd3

Joining : sw-rnd3

Failed to join : sw-rnd3

Join result 1025: Some part of the join process did not complete

0 Likes
Reply
1 Solution
New Contributor II

EAP-TLS connection is working now. The culprit was a certificate and key that

was generated on a Windows 8 machine. When the key and

certificate regenerated on a Windows 7 machine was used, the connection

worked. Thank you.

View solution in original post

0 Likes
Reply
9 Replies
New Contributor II

Here is an update. This was run on 3.6.2.

ssl_handshake_client_async is returning 0xfc00

 

Console app

> join_ent sw-rnd3 eap_tls wpa2

Joining : sw-rnd3

Supplicant received link event

TLS handshake failed

Supplicant received link eventFailed to join : sw-rnd3

Joining : sw-rnd3

Supplicant received link event

TLS handshake failed

Supplicant received link eventFailed to join : sw-rnd3

Joining : sw-rnd3

Supplicant received link event

TLS handshake failed

Supplicant received link eventFailed to join : sw-rnd3

Join result 1007:

Supplicant error 2

0 Likes
Reply
Contributor II

markmendelsohn

Do you change any thing in test.console source package ?

If not! It fail as expected!

Do you import the root CA used by test.console into your radius server ?

And do you replace root CA in your test.console with root CA of your radius server ?

All mention above is locate in libraries/utilities/command_console/wifi/certificate.h !

New Contributor II

As previously mentioned, know good keys and certificates were tested

on Android, iOS and OSX. These were then added to the certificate.h

file, rebuilt and downloaded into Dev kit for testing,

0 Likes
Reply
New Contributor II

Still more info:

The x509parse_key is failing as returned up from rsa_check_privkey library function.

  Our keys are good because they work on Windows. Android, OS X and IOS. They

were generated by the Windows Server. So there must be a specific type of key

the routine is looking for.

0 Likes
Reply
Moderator
Moderator

markmendelsohn

I wanted to let you know that the developers are looking into this issue.

0 Likes
Reply
New Contributor II

EAP-TLS connection is working now. The culprit was a certificate and key that

was generated on a Windows 8 machine. When the key and

certificate regenerated on a Windows 7 machine was used, the connection

worked. Thank you.

View solution in original post

0 Likes
Reply
Moderator
Moderator

Thanks for reporting the solution back to the thread markmendelsohn

0 Likes
Reply
Honored Contributor

markmendelsohn wrote:

EAP-TLS connection is working now. The culprit was a certificate and key that

was generated on a Windows 8 machine. When the key and

certificate regenerated on a Windows 7 machine was used, the connection

worked. Thank you.

This is a good finding, but it means something the SDK needs to address.

Asking a win8 user to downgrade OS to win7 is generally not an option.

0 Likes
Reply