Rob Withers wrote:
> 
> Ok, I am seeing four different classes of failures/errors in the
> NetworkSocketOpenTest.  Most of the failures are the error code problem
> from the Resolver tests.  The other failures are occuring because the
> Socket>>remotePort call is returning 0 rather than the remote port that
> the test thinks it has.
> 
> There are two errors:
> 
> NetworkSocketOpenTest>>testCheckSocketUtilities is an error on a ping:
> It looks like the the otherEnd closed, and there is a send data timeout
> exception on sendData: in the ping: method.  It hasn't even gotten to
> the waitForDataUntil: yet.
> 
> NetworkSocketOpenTest>>testSocketListenAccept is a primative error on
> #primAcceptFrom:receiveBufferSize:sendBufSize:semaIndex:
> 

I'm trying...:)   I recompiled some fprintf into the sqSocketRemotePort
code.  Here are the values I got for several tested values in there:

sqSocketRemotePort(peername  -1,  AF_INET  2,  socketFamily  10273)

It looks like the socket family is wrong for some reason.   I don't
think I can test this one further, as I've never tested the contents of
a sockstruct before...sorry.



A separate problem that I am having is another configuration problem. 
It happens intermittently.   Where the NetNameResolver localHostAddress
will return ByteArray(127 0 0 1), a connected Socket  sent localAddress
returns my cable modem address.  This fails several checkConnectedSocket
calls.  The wierd thing is that it comes and goes between different
image startups but no change to the network configuration of my machine
has occured.  Perhaps an intermittent network failure along the cable
modem net causes this???    WHat is the configuration expectation for
localHostAddress?

regards,
Rob