Quick update, still testing I did find that the Xilinx Webserver was very buggy, I did in fact start with the Xilinx examples, but then relied heavily on the lwip examples to fix the bugs.
Before upgrading the whole Xilinx EDK, I decidded to try a shortcut and replaced the Xilinx lwip sources with the latest lwip 1.3 source. To my surprise it compiled and, and as of now the server has been working for just under an hour with no duplicate acks, or window buffer leaks..... I need to perform more tests to ensure that all is okay Many thanks to all who replied to my call for help! Thanks Dave -----Original Message----- From: lwip-users-bounces+d.ward=sstl.co...@nongnu.org [mailto:lwip-users-bounces+d.ward=sstl.co...@nongnu.org] On Behalf Of David Ward Sent: 22 June 2009 14:42 To: Mailing list for lwIP users Subject: RE: [lwip-users] Window memory leak from retransmitted packets With TCP_QUEUE_OOSEQ = 0 the link is established but my tacp_Recvd() callback never fires. I have checked the xilinx documentation for lwip 2.00.a (dated Jan 2007) and it appears that Xilinx are using lwip stack version 0.7.2 ! Thanks for your help Dave -----Original Message----- From: lwip-users-bounces+d.ward=sstl.co...@nongnu.org [mailto:lwip-users-bounces+d.ward=sstl.co...@nongnu.org] On Behalf Of Kieran Mansley Sent: 22 June 2009 13:04 To: Mailing list for lwIP users Subject: Re: [lwip-users] Window memory leak from retransmitted packets On Mon, 2009-06-22 at 12:32 +0100, David Ward wrote: > Hi > I wonder if anyone can help with a lwip problem on a Xilinx ML506 > Virtex 5 evaluation board with a microblaze processor and Xilinx Lwip > 2.0 Any idea what version of lwIP that corresponds to? We're still on 1.3.0 as the most recent release. > We are using the raw packet implemetation with a single TCPIP socket > link between a windows PC and the development board. I have based my > code on the Xilinx web server examples. > > Our link connects and runs for a while, then fails. > Investigating with wireshark shows that on occasion lwip fails to ack > a packet or two causing the PC to perform a fast re-transmission, lwip > transmits an ack and the link re covers, except that our window size > has reduced by the size of the re-transmitted packet. It is this > 'window buffer leak' that causes the link to fail eventually. > > Is there anything I am missing, or that I need to do to clear out > duplicate packets? You could try disabling TCP_QUEUE_OOSEQ and see if your problem goes away. If it does, that suggests packets aren't being from from the out- of-order segment list. Kieran _______________________________________________ lwip-users mailing list lwip-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/lwip-users This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. _______________________________________________ lwip-users mailing list lwip-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/lwip-users This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. _______________________________________________ lwip-users mailing list lwip-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/lwip-users
