[Fwd: Re: [lwip-users] Closing connections]

[K.J. Mansley]

Message forwarded as original author was having problems posting to the
list.  I can answer the last point straight off: yes, both sides of the
connection are closed separately (by the two ends) and so you can still
received a FIN even if you've called tcp_close().

Kieran

-----Forwarded Message-----

From: Bonny Gijzen <address@hidden>
Subject: Re: [lwip-users] Closing connections
Date: 05 Oct 2004 22:29:22 +0200

Hello Kieran,

I think I still can't send to the mailinglist, so hereby I forward this
email to you. Perhaps you can post on the list, or maybe you can answer
it yourself.

My port and app are working pretty well at the moment.
I am just messing a little with detecting if the other side has closed
the connection.

I am using the receive callback and checking if the pbuf==NULL as the
documentation/source suggests.

However, I have noticed that this callback is called multiple times with
pbuf==NULL which has got me confused a little.
Can somebody enlighten me a little on tcp's and lwip's behaviour when a
connection has been closed from the other side?

Also, if my app determines to close the connection then I call
tcp_close(), is it possible then that also the callback gets called with
pbuf==NULL ?? (because other sides still sends its FIN ?)


Thanks for answers, and thank you for a nice stack.

Rgs Bonny,