[En-Nut-Discussion] Blocked NutTcpAccept ?

[Harald Kipp]

Petr,

Sure, that the socket from the last connection has been
properly closed?

Does Ethereal show FIN and its ACK? If that it missing
(peer killed the hard way) there is no chance for a TCP
receiver to detect a broken connection. (Except keepalive,
which is not available in Nut/OS.) Would a receive timeout
help (see NutTcpSetSockOpt())?


There had been a few fixes (ARP, IP) during the last weeks.
Did you try version 4.2? If the problem still exists with
this version, we may add it to the bug list.
http://sourceforge.net/tracker/?group_id=34079

Harald


>Everything works fine when the server is connected to the network.
>
>When I disconnect the server, the thread awaiting connections from a 
>client blocks and  doesn't accept any new connections.
>Socket is correctly created, but it hangs on NutTcpAccept(). And the 
>thread isn't resumed (it's still in the sleep state), when some client is 
>trying to connect.