|
From: | Bryan Schwichtenberg |
Subject: | [lwip-devel] [bug #19162] lwip_sendto: possible to corrupt remote addr/port connection state |
Date: | Wed, 21 Mar 2007 14:07:07 +0000 |
User-agent: | Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) |
Follow-up Comment #11, bug #19162 (project lwip): Hello, I was also thinking that adding a new api message could be a good solution. In reference as to why an ICMP destination unreachable is sent I think I have the answer. When the TFTP client requests a file from the server it connects on a well known port (69). The file transfer actually happens on a ephemeral port (usually in 32000 to 33000 ish range). When the failure occurs the pcb hasn't closed it connection to port 69 yet when the first data packet from the file transfer is sent on the ephemeral port. This results in lwIP notifying the server that the destination is unreachable (I assume because it thinks its connection is currently in use). _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?19162> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |