TCP: connection state not closed after passive close when still data in receive buffer about picotcp HOT 6 CLOSED

Could you provide a wireshark log for this?

from picotcp.

Duplicates bug #15

from picotcp.

This is not a duplicate of #15.
This refers the ep->state in the mbed socket interface, which is never changed even if the FIN comes.
The garbage collector from within the stack has nothing to do with this.

from picotcp.

I made a short TCP connection test: while(1){} after picotcp (TCP Server) accept the client.
Results: all received data (from Linux client) are stored in picotcp (TCP Server) input buffer => FIN sends from Linux client to picotcp => in picotcp side FIN aren't received => ep->state remain in SOCK_CONNECTED state

from picotcp.

After 4WHS closing, picotcp buffer isn't empty => TCP protocol sends PICO_SOCK_EV_RD to user and in wakeup() function (stack_endpoint.cpp file) socket state is changed to SOCK_CONNECTED:

if ((ev & PICO_SOCK_EV_CONN) || (ev & PICO_SOCK_EV_RD)) {
ep->connected = 1;
ep->state = SOCK_CONNECTED;
}

Proposed solution: remove PICO_SOCK_EV_RD check:

if (ev & PICO_SOCK_EV_CONN)) {
ep->connected = 1;
ep->state = SOCK_CONNECTED;
}

from picotcp.

Issue fixed in revision 60.

from picotcp.