• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 45 subscribers
  • Views 3198 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SNI Support

Garrett Albers
Prodigy 90 points
Other Parts Discussed in Thread: CC3200, CC3100

Hello!

Does the CC3200 support SNI on the client?

https://en.wikipedia.org/wiki/Server_Name_Indication

Thanks for the help!

  • 0
    TI__Guru* 85400 points
    Hi,

    Please see: e2e.ti.com/.../422647

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Prodigy 120 points

    Hello,

    The mentioned thread refers to CC3100, but I assume the informatin in ii is valid for CC3200 as well; in this case, could you confirm that a new CC3200 hardware version will be needed to have SNI support? And is there a timeline for such support?

    Thank you

  • 0 in reply to Francesco Lavra
    TI__Expert 3765 points

    Hi Francesco,

    I think that there was a misunderstanding in the SNI requirement.  

    This feature is used in order to connect different host servers on the same port - it's not planned to be supported.

    The confusion came from the feature we added to SDK1.2 to verify the domain server name.

    I'm sorry for this confusion.

    Best Regards,

    Nir Nitzani

  • 0 in reply to Nir Nitzani
    Prodigy 10 points
    Hi,

    I'm getting SSL handshake error (-340) while connecting CC3200 to a Amazon AWS server using SNI.

    I just realized this might be a show stopper for my project and I'd like to get final confirmation to the issue.

    Will/does CC3200 support SNI or is there any way to get past this issue (custom socket library, another product, ...)?

    AFAIK, from SSL client's point of view it should be enough to send server name during the initial handshake...


    Thanks,

    Aki
  • 0 in reply to Aki Lempinen
    Prodigy 70 points

    Same question here.  I have a CC3200 project, and I cannot connect to AWS API Gateway using a custom domain name that requires SNI.  The HTTPCli_connect API returns -102 despite having a valid root certificate file.  Does the latest CC3200 SDK support SNI?  If not, when?

    Thanks,

    Clinton Knight

  • 0 in reply to Clinton Knight
    Guru 79905 points

    Hi Clinton,

    Answer at 2nd post is clear (https://e2e.ti.com/support/wireless_connectivity/simplelink_wifi_cc31xx_cc32xx/f/968/t/422647). There is not planned to add SNI support into CC3200. From that answer I am not sure, but also it looks that SNI will not be supported at new CC3220.

    Jan

  • 0 in reply to Jan D
    Prodigy 70 points
    Jan, thanks for the response. It's really surprising and inexcusable that SNI isn't supported, as that's the default for AWS CloudFront services such as API Gateway. Couple that with scattershot documentation, flaky tools, and buggy & crash-prone SimpleLink WiFi drivers, and despite being well advanced with custom hardware, we've abandoned the CC3x00 solution as not being suitable for commercial applications. The concept is sound, the silicon may be great, and we found TI-RTOS to be pretty solid as well, but our experience developing with the SL solution was beyond awful.
  • 0 in reply to Clinton Knight
    Guru 79905 points
    Hi Clinton,

    I don't agree. I am working with CC32x0 more than two year and I am not experiencing any stability issue. I agree that inexperienced developer or developer which haven't enough time to study and adopt whole platform, can have issue with CC3200.

    CC3x00 devices are good and stable platform in comparison with competitors. CC3x00 devices are used in many commercial products. Awful and unstable was old CC3000 devices. But CC3200 is not bad and CC3220 is even better.

    Jan