Endpoint T_DATAXFER -> T_IDLE weirdness
Endpoint T_DATAXFER -> T_IDLE weirdness
- Subject: Endpoint T_DATAXFER -> T_IDLE weirdness
- From: Jen Beaven <email@hidden>
- Date: Wed, 6 Apr 2005 13:38:14 -0400
How is it possible for an endpoint to go from T_DATAXFER state to
T_IDLE state without either end issuing a disconnect request?
I do a bind, then connect, then accept the connection and verify the
(sync, blocking) endpoint is in the T_DATAXFER state. Then try to
send a packet, to find the endpoint has gone to T_IDLE. I have not
diconnected, nor have I received any event since the T_CONNECT. So
how can this happen?
It's happening on one model of a series of devices which all use the
same API. None of the others show this behavior. This is the first
device made by a new vendor - my code has been working forever on the
other devices. The PC version has no problem, of course.
The only anomalous thing I see in Ethereal traces is that the new
device does a duplicate ACK almost every time it ACKs. Is that
something that would anger the mac but that the more
forgiving-of-evil-code PC would put up with?
t.i.a.
/jen
--
http://pengcognito.com - weekly penguin cartoon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden