lwip-users
[Top][All Lists]
Advanced

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

SV: [lwip-users] Re: TCP_SEG Leak ...


From: Jan Wester
Subject: SV: [lwip-users] Re: TCP_SEG Leak ...
Date: Wed, 5 Dec 2007 15:51:02 +0100

Hi
Can you send me the fix for ooseq, I belive I have the same problem with my webserver with more simultane connections
 

Med vänlig hälsning/Best Regards
Jan Wester

_________________________________

WHI Konsult AB

Scheelegatan 11, 112 28 Stockholm, Sweden
www.whi.se
address@hidden
+46 8 449 05 30

 


Från: address@hidden [mailto:address@hidden För Thomas Catalino
Skickat: den 3 december 2007 02:33
Till: address@hidden
Ämne: [lwip-users] Re: TCP_SEG Leak ...


Simon -

Thanks for confirming the bug. We'll put a patch in our code for now and will watch the bug for the real fix. Let me know if I can help, I would have suggested a fix, but I'm not familiar enough with the ooseq processing in the stack.

As you can imagine this is eventually fatal -- especially for applications that make / break a lot of TCP connections (we do a lot of HTTP GETs and POSTs and is how we discovered it).

Thanks again -
Tom


reply via email to

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