[En-Nut-Discussion] TCP Socket waiting in TCPS_CLOSE_WAIT

Stephen Noftall stephenn at lcsaudio.com
Fri Mar 7 02:31:21 CET 2003

Hi, hopefully a simple answer to this one:

In my app, I wait on a tcp connection. When it's available, I read and write
it using NutTcpSend() and NutTcpReceive().

Everything seems to be working ok, I can connect and send and receive data
via a remote telnet app.

My problem is that when my remote telnet application closes, I am expecting
the Ethernut to generate and error in NutTcpSend() or NutTcpReceive(). I was
hoping it would generate the ETIMEDOUT or something similar. My problem is
that my Ethernut application just sits there, and never errors out. Of
course, when I try to connect again with my telnet app, it refuses the

When I look at the sockets via my debug RS422 port (allways have to have one
of those ;-), it shows the TCP socket in the TCPS_CLOSE_WAIT state.

Does anyone have any ideas what I could try? I tried to change the timeout
values, but they did not seem to help.

Any help would be appreciated.


Stephen Noftall

More information about the En-Nut-Discussion mailing list