Re: [ECOS] Re: __tcp_close() can't close connection in Redboot

[Andrew Lunn <andrew at lunn dot ch>]

On Wed, Oct 12, 2005 at 07:55:11AM -0500, Grant Edwards wrote:
> In gmane.os.ecos.general, you wrote:
> 
> >   I am trying to build up httpd service in RedBoot.
> > And I met problem that I can't close connection by
> > calling __tcp_close() after replying data to
> > client,and the httpd sock state is always TIME_WAIT.
> 
> Right. 
> 
> After you close a tcp connection (you send a FIN packet and
> receive a FIN back) the state is _supposed_ to be TIME_WAIT.
> 
> http://tangentsoft.net/wskfaq/articles/debugging-tcp.html

The purpose of this is to catch old packets still floating around the
network including retransmitted FIN packets.

Normally this is not a problem. The server goes back to its listen
socket and accepts the next connection.  After 2x maximum segment
lifetime the old socket in TIME_WAIT is destroyed. 

I don't know the redboot tcp stack. Does it implement the same
concept? ie simply accept the next connection waiting on the listen
socket?

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss