Tcp/Ip Error Messages; Overview Of The Ssl-Relevant Messages - Abus SECVEST FUAA50 Series Installer Manual

TCP/IP error messages

The following table shows the TCP/IP error messages:
1001 General Error
1002 Invalid socket descriptor
1003 Invalid parameter
1004 It would have blocked
1005 Not enough memory in memory pool
1006 Connection is closed or aborted
1007 Socket is locked in RTX environment
1008 Socket, Host Resolver timeout
1009 Host Name resolving in progress
1010 Host Name not existing

Overview of the SSL-relevant messages

The following table shows SSL-relevant messages that are used in the SSL stack – these may change in
a future update:
10064 Failed to get an IP address for the given hostname
10066 Failed to open a socket
10068 The connection to the given server / port failed
10070 Binding of the socket failed
10072 Could not listen on the socket
10074 Could not accept the incoming connection
10076 Reading information from the socket failed
10078 Sending information through the socket failed
10080 Connection was reset by peer
10082 Connection requires a read call
10084 Connection requires a write call
37520 A counter would wrap (eg, too many messages exchanged).
37648 Internal error (eg, unexpected failure in lower-level module)
37776 Unknown identity received (eg, PSK identity)
37904 Public key type mismatch (eg, asked for RSA key exchange and presented EC key)
38032 Session ticket has expired.
38160 Processing of the NewSessionTicket handshake message failed.
38288 Handshake protocol not within min/max boundaries
38416 Processing of the compression / decompression failed
38544 Hardware acceleration function skipped / left alone data
38800 The requested feature is not available
38928 Bad input parameters to function
39056 Verification of the message MAC failed
39184 An invalid SSL record was received
39312 The connection indicated an EOF
39440 An unknown cipher was received
39568 The server has no ciphersuites in common with the client
39696 No RNG was provided to the SSL module
39824 No client certification received from the client, but required by the authentication mode
39952 Our own certificate(s) is/are too large to send in an SSL message
40080 The own certificate is not set, but needed by the server
40208 The own private key or pre-shared key is not set, but needed
40336 No CA Chain is set, but required to operate
40464 An unexpected message was received from our peer
40592 A fatal alert message was received from our peer
40720 Verification of our peer failed
Appendix
293