[lwip-devel] [task #10370] Raw API: Callback for received FIN to confirm connection is closed

[Iordan Neshev]

Follow-up Comment #6, task #10370 (project lwip):

Finally, I found the time to check this.

It works as expected in the normal case.

>- no more rx packets after calling tcp_close, 
>- if there is unacked rx data (i.e. the receive window is not >at its full
size) or data arrives after we called close: RST is >sent and the connection
is aborted

I was not able to test these cases. I'm not quite sure that the connection
should be aborted. Sending RST is good, but the abort callback my mislead the
application. At the time I call tcp_close/shutdown, the peer's data may be
already present on the wire (worst case is GPRS net where the lags are usually
more than a second). When I call tcp_close usually I don't care if the peer
tells me something more. Probably I'll rise a flag before calling
tcp_close/shutdown and if the abort callback fires, I'll ignore the error if
this flag is raised.

Just to be clear: I don't want to adapt lwip to my application, but to do
what is logical, following the standards. Of course I will adapt my
application instead. The problem is that I'm not sure what is the right
behavior. 

Thanks for fixing this issue! 




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?10370>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/