Calling socket connect() triggers errno=95

[Loren Rogers]

Hello,

I am offloading sockets in config.  I instantiate a socket, set the send/recv timeouts, and then call connect().  It's returning a 95 which is EOPNOTSUPP.  I was able to step via debug all the way down to a nrf_connect().  But that was it.

Anyone have any ideas of what I'm doing wrong?

/Loren

[Loren Rogers]

I realized that the server(s) I was trying to connect to didn't support the ciphers that the nrf modem does.  I did manage to find a server that support ONE of the ciphers that the modem does (*CBC*).  However, I downloaded the 1.3.1 mfw and ran a wireshark trace.  Indeed I saw the GCM_SHA384 cipher selected from the server!  Thank you Nordic!  So if you happen to run into this, making sure your server supports the modem's cipher list is a good start.