MDK MIDDLEWARE: TCP-ERR:Socket #, Out of range segment received

Information in this knowledgebase article applies to:

• MDK v5.x
• MDK Middleware Network Component v7.x

SYMPTOM

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

CAUSE

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.

RESOLUTION

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:

• If you suspect the receive buffer is being overwhelmed on the microcontroller, you can increase the Receive Window Size, in the file "NET_Config_TCP.h". Also, check if the system core clock is configured correctly, and if the clock speed can be raised.
• Lowering the receive Maximum Segment Size (MSS) on the microcontroller, in "NET_Config_TCP.h". The range is between 536 and 1460 bytes, inclusive. This value is part of network discovery, and can lower the size of a packet sent to the device. Some types of networks may require a lower MSS, overall. If the change reduces the number of re-transmissions, you may also see improved network responsiveness.
• In general, upgrade to the latest version of the Network Component and Ethernet CMSIS drivers. Improvements and fixes related to both receiving packets and recovering lost packets can be added over time.
• If the issue persists, or if the out-of-range error is followed by other types of error messages, users with support agreements may contact Keil tech support, who can assist with troubleshooting and answer questions about the Network Component.

MORE INFORMATION

• Refer to User API for TCP Sockets for a procedural overview of TCP communication.
• Refer to RFC 5681, TCP Congestion Control

SEE ALSO

• MDK MIDDLEWARE: How to modify TCP Tx MSS
• MDK MIDDLEWARE: Extending secure services for data rich apps
• MDK MIDDLEWARE: Fail to send data due to too small TCP window size

FORUMS

• TCP ERR: Out of range sequence number received
• File upload through HTTP problem

Last Reviewed: Tuesday, January 5, 2021