Thanks for your response.

But the same logic does not apply for tcp_lo_select.c

The output of tcp_lo_select.c is shown below.

Start TCP server - test
TCP SERVER: Hello eCos network
Start TCP client 1 - test
client 1 :started
Start TCP client 2 - test
client 2 :started
TCP SERVER connection from 127.0.0.1: 9990
TCP SERVER connection from 127.0.0.1: 9991
SERVER : Client 1 is alive. You may continue ....
SERVER : Client 2 is alive. You may continue ....
PASS:<Server returned OK>
EXIT:<done>

Here we get loop back address from the client. In this test also 
we don't have any explicit binding for the client socket then how 
does it display the loopback address?

Regards,

Kaustubh

On Thu, 07 Mar 2002 Gary Thomas wrote :
>On Thu, 2002-03-07 at 06:05, Kaustubh Purandare wrote:
> > Hi,
> >
> > The tcp_lo_test.c displays the following result after
> > executing on synthetic linux platform.
> >
> > Start TCP server - test
> > TCP SERVER: Hello eCos network
> > Start TCP client - test
> > client:started
> > TCP SERVER connection from 0.0.0.0
> > SERVER : Client is alive. You may continue ....
> > PASS:<server returned OK>
> > EXIT:<done>
> >
> > I understand that it runs a loop back test so the address
> > displayed should be 127.0.0.1 and not 0.0.0.0
> >
> > Is there a bug in the test?
>
>The test checks that a connection can be made *to* a server
>on the loopback address.  The message you see is where the
>connection came *from*.  Since I don't see any explicit
>binding on the source address, 0.0.0.0 seems like the right
>value.
>


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