[lwip-devel] [bug #39340] Raw API changed regarding TCP connections closing

[Bill Auerbach]

URL:
  <http://savannah.nongnu.org/bugs/?39340>

                 Summary: Raw API changed regarding TCP connections closing
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: billauerbach
            Submitted on: Tue 25 Jun 2013 09:18:11 AM EDT
                Category: None
                Severity: 3 - Normal
              Item Group: Faulty Behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: 1.4.1

    _______________________________________________________

Details:

There is a condition in lwIP when a connection is closed by the remote end
that the tcp_recv callback is not called with a NULL pbuf pointer to signal
the connection was closed.  The documented behavior in rawapi.txt in the 1.4.1
release is that it should.


The current behavior is that the tcp_err callback is called instead of the
previous method of calling tcp_recv when recv_flags has TF_RESET set.  This is
at line 307 in tcp_in.c.  This could be happening because Win7 is closing
connections with TF_RESET set.  I was using XP until a few months ago when the
documented behavior is followed.  The remote socket is closed normally.

Is TF_RESET an error?  Even if tcp_err is called, shouldn't tcp_recv still be
called with NULL pbuf to keep the notification consistent?




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?39340>

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