You copied the Doc URL to your clipboard.

A.1. ENP_ error codes

The error codes listed in Table A.1 are used throughout the stack. Success is zero, definite errors are negative numbers, and indeterminate conditions are positive numbers. These codes are provided in ipport.h. You can modify them to wrap around an existing system.

Note

If you define errors with non-negative values, the stack does not work.

These error codes are typically returned by functions that return an integer. See the function specifications (Chapter 3 TCP/IP API Functions and Chapter 6 Low-overhead UDP Functions) for information on specific functions.

ENP_ error codes
Error typeError code (defined in ipport.h)Return valueDescription
No errors:SUCCESS0Success
 OK0Success
Nonfatal/success:ENP_SEND_PENDING ARP_WAITING1ARP is holding the packet while awaiting a response from the target host
 ENP_NOT_MINE2The packet was of no interest (callback reply only)
Programming errors:ENP_PARAM–10Bad parameter
 ENP_LOGIC–11Illogical sequence of events
System errors:ENP_NOMEM–20malloc() or calloc() failed
 ENP_NOBUFFER–21Ran out of free packets
 ENP_RESOURCE SEND_DROPPED–22Ran out of queueable resources OR full queue
 ENP_BAD_STATE–23TCP layer error
 ENP_TIMEOUT–24Operation did not complete in reasonable time
 ENP_NOFILE–25Expected file was missing.
 ENP_FILEIO–26File I/O error
Net errors:ENP_SENDERR–30Send to net failed at a lower layer
 ENP_NOARPREP–31No ARP reply for a given host
 ENP_BAD_HEADER–32Bad header at the upper layer (for callbacks)
 ENP_NO_ROUTE–33Cannot find a reasonable next IP hop
 ENP_NO_IFACE–34Cannot find a reasonable interface
 ENP_HARDWARE–35Detected a hardware failure
Was this page helpful? Yes No