MDK MIDDLEWARE: TCP-ERR:Socket #, Out of range segment received
Information in this knowledgebase article applies to:
After MDK MIDDLEWARE: How to enable the network debugging in µVision, the Event Recorder shows the following error:
| Event | Time(sec) | Component | Event Property | Value | | 10 | 1.23456778 | Net_TCP | OutOfRangeSegment | sock=1 |
Earlier versions of the Network Component and TCPnet could report similar error messages via Debug STDIO (ITM or USART):
TCP-ERR:Socket #, Out of range SEQ number received TCP ERR: Out of range sequence number received
A packet is lost, at some point in the network.
Then a sender transmits the next (unexpected) segment number. The receiver detects this, and informs the sender of the expected number, by replying with a duplicate ACK. This ACK is based off the last segment that was handled. Recovery steps are implemented, by the Network Component, according to RFC 5681, TCP Congestion Control.
Although packet loss is common, when this error message is repeated continuously or associated with other error messages, it can indicate a larger problem, with either a sender or a receiver on the network.
There can be several different causes for packet loss, so multiple resolutions exist. To determine which node in the network causes the issue, the users can use third party tools, such as Wireshark, to help isolate the problem. For example, a router can dump packets if its receive buffer is overloaded. From the microcontroller side, you may try the following:
Last Reviewed: Wednesday, November 21, 2018
of your data.