[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #26069] Connect to a remote IP address which is not pr
From: |
Rikke Ottesen |
Subject: |
[lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang |
Date: |
Fri, 03 Apr 2009 08:13:32 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 |
Follow-up Comment #4, bug #26069 (project lwip):
Im not that into the pcb->nrtx part, but one thing I do no is that the
TCP_EVENT_CONNECTED() function is never called.
I have looked through all the code and the TCP_EVENT_CONNECTED() is ONLY
called when the connection is a success.
It is called in:
static err_t tcp_process(struct tcp_pcb *pcb);
So even though I wait a long time I never get a failure reply to the App.
I expect as the documentation says, that a failure should be retrieved when
the connection cannot be established.
The point is that the TCP_EVENT_CONNECTED() should be called somewhere if the
connection is never established, the question is where it should be called.
I have looked on the site
http://en.wikipedia.org/wiki/File:Tcp_state_diagram_fixed.svg as I see it the
pcb should be closed/freed if the connection is not established, and the
TCP_EVENT_CONNECTED() should be called with a failure.
Does this make sense? :)
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?26069>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Rikke Ottesen, 2009/04/02
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Rikke Ottesen, 2009/04/02
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Kieran Mansley, 2009/04/02
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Rikke Ottesen, 2009/04/02
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Kieran Mansley, 2009/04/02
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang,
Rikke Ottesen <=
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Kieran Mansley, 2009/04/03
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Rikke Ottesen, 2009/04/03
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Oleg Tyshev, 2009/04/03
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Rikke Ottesen, 2009/04/03
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Kieran Mansley, 2009/04/03
- [lwip-devel] [bug #26069] Connect to a remote IP address which is not present makes the APP hang, Rikke Ottesen, 2009/04/03
- [lwip-devel] [bug #26069] Documentation of tcp_connect() incorrectly describes handling of errors, Kieran Mansley, 2009/04/03
- [lwip-devel] [bug #26069] Documentation of tcp_connect() incorrectly describes handling of errors, Rikke Ottesen, 2009/04/03
- [lwip-devel] [bug #26069] Documentation of tcp_connect() incorrectly describes handling of errors, Kieran Mansley, 2009/04/03
- [lwip-devel] [bug #26069] Documentation of tcp_connect() incorrectly describes handling of errors, Rikke Ottesen, 2009/04/03