Thanks Jan. I tried setting TCP_WND_UPDATE_THRESHOLD to 0 and I still get the same behaviour of decreasing window size. I then reverted to 1.3.0 and the window size stays constant as expected. I would stay at 1.3.0 if I could but I need a fix that 1.3.1 has. Any help would be greatly appreciated.
Thanks, Dave -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jan Wester Sent: Friday, October 16, 2009 7:42 AM To: 'Mailing list for lwIP users' Subject: SV: [lwip-users] TCP payload is doubled Hi I have the same problem Kieran mention about to set TCP_WND_UPDATE_THRESHOLD = 0. I have not tested yet, will start to test next week Kieran wrote The window advertisement code was re-worked in 1.3.1 to only send an explicit update when the change in window is greater than TCP_WND_UPDATE_THRESHOLD. This defaults to (TCP_WND / 4). You could define this to be zero to get the old behaviour, but the new behaviour should be much better. I would be interested to know what the problem you encounter as a result of the less-frequent window updates is. Note that any ACKs for data that get returned should have the up-to-date window information in them - it is only the sending of explicit window update ACKs that is restricted. /Jan -----Ursprungligt meddelande----- Från: [email protected] [mailto:[email protected]] För David Shmelzer Skickat: den 15 oktober 2009 21:56 Till: Mailing list for lwIP users Ämne: RE: [lwip-users] TCP payload is doubled I did a wireshark capture and the window size from lwip keeps decreasing by the packet length received by lwip for each transaction. When it finally decreases to less than the packet size my s/w hiccups because it expects a full packet. So this problem exposed a flaw in my software. Is anyone else seeing teh window size decreasing? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bill Auerbach Sent: Wednesday, October 14, 2009 8:13 AM To: 'Mailing list for lwIP users' Subject: RE: [lwip-users] TCP payload is doubled >Occasionally, the payload in my TCP return packet sent from lwip is >more bytes than I'm expecting. >It looks like it may be concatenating two copies of the payload. Does this mean the data received by the application is bad or you're just receiving more of it than you expected but it's all good? Bill _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
