On Sun, Aug 03, 2014 at 16:21:07 +0400, Mark Lvov wrote:
This is exactly what I've done, only I have a class, each instance of which
manages a connection to a particular endpoint (only, my state enum has
ACTIVE_CLOSE and PASSIVE_CLOSE instead of CLOSING, since those are handled
differently).
Hi,
if you do need to detect a particular situation on tcp_err(), then you
can use the arg parameter. You are not getting the pcb because, afaik,
it no longer exists; it has been removed and freed before calling the
callback function; see tcp.c line 393 for example
The tcp_err() callback that
Hello,
It seems, I still have some unanswered questions with regard to
correct connection teardown. Let's consider the active close situation
(we are closing the connection). We've just called tcp_closed and are
waiting for the tcp_recv callback to be called with an empty pbuf.
But, as I
Il 02/08/2014 20:52, Mark Lvov ha scritto:
Hello,
It seems, I still have some unanswered questions with regard to
correct connection teardown. Let's consider the active close situation
(we are closing the connection). We've just called tcp_closed and are
waiting for the tcp_recv callback to
Counter-proposal:
Read the wiki, and if it is not clear enough, I will change it
http://lwip.wikia.com/wiki/Raw/TCP
Regards
--
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Well, shame on me!
I was actually using
http://git.savannah.gnu.org/cgit/lwip.git/tree/doc/rawapi.txt?id=5b8b5d459e7dd890724515bbfad86c705234f9ec
as a reference and it obviously lacks the details, that are present on
the page you've linked. All my questions are answered by that page,
thanks very
Hello,
I am using raw API, LWIP version is 1.4.1.
I am unsure, how to properly handle closing connections. I am considering
the following cases:
* passive close - remote host decided, that he is done with us and sent
FIN. We see it, when we receive a NULL pbuf. Is the pcb deallocated by that
