Re: RE : [lwip-users] Receiving RSTs

[Jonathan Larmour]

Frédéric BERNON wrote:
>>Receiving an RST triggers the err_tcp() error function which posts a
> NULL message. It appears that the mbox is getting populated with NULL
> messages, but these messages are not being read out at all, and so the
> mbox is getting full.
>  
> I'm not sure it's the case in last CVS HEAD: when err_tcp is called and
> when we are in "connect" step, a NULL message is post in conn->mbox, and
> since the calling thread is waiting this event, the netconn_connect
> return, and the calling thread have to close the socket. During the
> close, any message in conn->mbox is "drained".

I wonder from what Aparna says:

>>         When the Windows server is not up, the PC responds with a RST
>>         for a received SYN. The connect() API returns an error, and the
>>         client retries connect() after every few seconds.

whether he/she is not closing the socket before calling connect again?

Maybe the netconn API needs to explicitly disallow connects if conn->err is
set?

Either way, if the socket isn't being closed, Aparna needs to fix his/her code.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine