Roger Cover wrote:
I am not familiar with the internal organization of the lwIP library. Which
debug statements should I turn on to find out what is happening in this case?
I'm sorry but I cannot tell you that right now. The simplest thing would
be to get someone with more knowledge to
-
From: lwip-users [mailto:lwip-users-bounces+rcover=specinst@nongnu.org] On
Behalf Of Simon Goldschmidt
Sent: Thursday, September 29, 2016 11:14 PM
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] Unusual termination of a TCP connection.
Roger Cover wrote:
> Thank you all for y
Roger Cover wrote:
> Thank you all for your replies.
No answer often means noone knows what your problem is.
> [..] the lwIP 1.2.0 server always sends ACKs for the request (GET or POST)
> packets before sending the data requested. [..]
> The lwIP 1.4.1 server sends the requested data before
Of Roger Cover
Sent: Wednesday, September 28, 2016 1:34 PM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] Unusual termination of a TCP connection.
Greetings,
In the Wireshark capture that I sent in my original post, the data sent from
the server is ACKed by the same packet
+FIN instead. Why are the
two different?
Regards,
Roger
-Original Message-
From: lwip-users [mailto:lwip-users-bounces+rcover=specinst@nongnu.org] On
Behalf Of goldsimon
Sent: Wednesday, September 28, 2016 1:22 PM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] Unusual
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.
Simon
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 28. September 2016 7:32:05 nachm. schrieb Roger Cover
: [lwip-users] Unusual termination of a TCP connection.
I see what you mean.
I also see that the 1.2.0 version sent content-length=0 and the 1.4.1 version
sends content-length=115 IIRC, this is not unusual, lwIP might be indicating
that there is still data to be sent. Is it possible that you left
I see what you mean.
I also see that the 1.2.0 version sent content-length=0 and the 1.4.1
version sends content-length=115
IIRC, this is not unusual, lwIP might be indicating that there is still
data to be sent. Is it possible that you left some data in the buffer ?
Thank you very much indeed
Greetings,
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
