lwip-users
[Top][All Lists]
Advanced

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

Re: [lwip-users] Duplicate ACK problem with LWIP 1.3.2


From: Hafiz Bashir
Subject: Re: [lwip-users] Duplicate ACK problem with LWIP 1.3.2
Date: Wed, 06 Jan 2010 16:55:53 +0000
User-agent: Thunderbird 2.0.0.23 (Windows/20090812)

Hi,

I seem to have a problem sending the complete Wireshark capture file (is there a limit of the attachment size ?), so I have just sent the first 200 packets which does show the problem

Best Regards

Hafiz

address@hidden wrote:
Please attach wireshark captures in wireshark's own file format, not as text export or any other format to make sure they are readable.

Simon


Hafiz Bashir wrote:
Hi,

We seem to have a problem when using LWIP 1.3.2 to request a large file from a remote server. Our target is an ST7101 running OS21.

Our application uses the netconn API to request a large file from a remote server using HTTP GET

From what I can see from Wireshark, the transfer begins OK with correct ACK's being sent.

However at what appear to be random points during the transfer, I start to see duplicate ACK's. It seems LWIP is sending the same ACK for the next few segmemts it receives.

I have experimented with adjusting the TCP_WND size in lwipopts.h with mixed results. It would appear that if TCP_WND > 8*TCP_MSS, then we start seeing the duplicate ACK problem. TCP_MSS is set to 1460. However having a lower TCP_WND size results in a lower transfer performance.

I have attached a text file containing the Wireshark export.

Any help would be greatly appricated.

Thanks

Hafiz

_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users

------------------------------------------------------------------------

_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users

Attachment: dup_ack_1_lwip_1_3_2.pcap
Description: Binary data


reply via email to

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