| Previous | Next |
| EADDRNOTAVAIL | EOPNOTSUPP |
ENETRESET
ENETRESET means that the network aborted the connection. It is a different diagnostic category from ECONNRESET: the latter identifies a reset by the peer, while ENETRESET describes a failure reported by the network side. The errno alone does not identify the exact device, route, tunnel, or policy event that produced it.
Treat the connection object as failed for the operation that returned the error. For a stateful protocol, reopening a socket and reconnecting may be necessary, but replaying application data is safe only when the application protocol defines how to detect duplicate or incomplete requests. This distinction matters for uploads, transactions, and commands that may have reached a peer before the local stack reported the failure.
What makes the diagnosis actionable
- Preserve the failing system call, its timestamp, socket family and type, local and peer addresses, and any preceding timeout or interface event.
- Compare the scope of the failure: one connection, one destination prefix, one interface, or every socket in the same network namespace.
- Inspect route and interface changes around the event, including VPN reconnects, Wi-Fi roaming, virtual-device recreation, and container-network updates.
- Keep protocol-level reconnect logic separate from transport telemetry so that a retry policy cannot hide repeated network resets.
Linux errno(3) · POSIX <errno.h> · Linux IP sockets
Looking for a different code? Search another status or error code.