stucked ESTABLISHED pcbs

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

stucked ESTABLISHED pcbs

koszo.simon
I try to create a simple tcp echo server which replies back whatever it has
received (I know that there are ready to use examples for this: I work based
on those examples...). It already works more or less however I found an
issue about stucked pcbs in ESTABLISHED state.

Here is the problematic process step by step:
1. Client established a connection with the server
2. I manually unplug the cable which is between two switches which are
between the server and the client device.
3. Client noticed that the cable is unplugged (I don't know exactly how) so
it closed the socket.
4. I plugged the cable back.
5. Client successfully connected however the previously used pcb got stucked
and still exists (its state is still ESTABLISHED).

Is there any tool which closes such stucked pcb-s? For example if I send any
message to this stucked pcb the acknowledgement obviously will not come
back: I debugged it and the tcp_sent() callback is not called however the
tcp_output() returned ERR_OK. Is there any built-in functionality which
closes the pcb if the acknowledgement is not received for a specific time?




--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users
Reply | Threaded
Open this post in threaded view
|

Re: stucked ESTABLISHED pcbs

koszo.simon
I have found the answer to my question: LWIP_TCP_KEEP_ALIVE:
http://lwip.100.n7.nabble.com/how-to-keepalive-in-raw-api-td2964.html
https://lwip.fandom.com/wiki/Raw/TCP



--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html

_______________________________________________
lwip-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/lwip-users