[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] Unusual termination of a TCP connection.

From: goldsimon
Subject: Re: [lwip-users] Unusual termination of a TCP connection.
Date: Wed, 28 Sep 2016 22:21:39 +0200
User-agent: AquaMail/ (build: 27000209)

A RST is sent when lwip knows that one of the two sides has not read (or packed) all data that has been sent. This is what standard socket stacks would do also.


Gesendet mit AquaMail für Android

Am 28. September 2016 7:32:05 nachm. schrieb Roger Cover <address@hidden>:


I have a server application using lwIP 1.4.1. When I use a Python program to connect to my server, the server always terminates the TCP connection with a RST instead of a FIN packet. The RST appears to be negatively impacting the performance of my communications. I have attached a Wireshark capture of the traffic in the attached file lwIP141.pcapng. In this file my server is at address

I previously implemented a server using the lwIP 1.2.0 library (about a decade ago), and did not encounter this problem. The attached file lwip120.pcapng is a Wireshark capture of the same Python program communicating with the old lwIP 1.2.0 server. In this file my server is at address Using lwIP 1.2.0 the TCP connection terminates normally with a FIN, FIN+ACK, ACK set.

Does anyone have any insight into why the RST is being issued? Is there anything I can do to eliminate this problem? I look forward to your reply.

Roger W. Cover
Spectral Instruments, Inc.
420 N. Bonita Ave.
Tucson, AZ 85745
520-884-8821 ext. 144

lwip-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]