Forced disconnection TCP Retransmission limit

[aughey]

I have an situation where, during an active TCP connection, the remote side is hard-reset. The remote side is a Windows machine in stealth mode, so it will not send RST messages for unconnected sockets. Smoltcp will do a retransmission backoff as expected, but it never times out and decides the remote side is gone.

In my application, I now run my own timeout for any writes to a socket that do not succeed within some time period. If "detected", I'll remove the socket from the interface. Is this the best way to handle this situation, or is there a better way to manage this exception condition?