I think someone should try to reprodude this problem on his/her plateform. Me I don't have much time right now, but if Chen can give the details of his program maybe it could be useful.
----- Original Message ----- From: "Kieran Mansley" <[email protected]> To: "Mailing list for lwIP users" <[email protected]> Sent: Friday, March 06, 2009 10:26 AM Subject: Re: [lwip-users] Re: tx badnwidth > On Fri, 2009-03-06 at 09:05 +0000, Kieran Mansley wrote: > > On Thu, 2009-03-05 at 18:14 +0100, [email protected] wrote: > > > Kieran Mansley wrote: > > > > You can probably get away with leaving TCP_WND alone > > > > if you're acting purely as a sender of packets, > > > In fact, I think you won't, as TCP_WND is not only the announced receive > > > window size but serves as a limit for transmit window, too. > > > > I thought that sounded familiar and had a look for it in the source > > before posting, but couldn't find where this happened. Can you remind > > me? > > I've had another look and still can't find this. The only bit that > might be what you're referring to is in tcp_connect(): > > pcb->snd_wnd = TCP_WND; > > However, pcb->snd_wnd will be overwritten with the real window size when > we get the SYN-ACK back from the other end. > > Kieran > > > > _______________________________________________ > 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
