Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

TCP 'soft' connection death.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

TCP 'soft' connection death.

Subject: TCP 'soft' connection death.
From: Matt Darland <email@hidden>
Date: Mon, 24 Apr 2006 15:22:27 -0500

	Hello all,

Scenario: 1. Via the KPI interfaces a TCP connection established to a remote machine. 2. Normal read/write flow of data occurs. 3. Peer goes away without performing TCP teardown (e.g. goes to sleep).

At this point, sock_sendmbuf() will happily take additional data, without returning an error. As of waiting about 3 minutes, none of the socket filter events get called.

Is the above behavior known to occur (i.e. should I be checking something else in my code)? Does the TCP stack believe the connection is still valid? Is there some way at the KPI level I can detect when TCP believes the connection to be dead, or am I not waiting long enough?

Thanks,
Matt Darland

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



Prev by Date:
BlueTooth spewage

Next by Date:
Kext fails to load when falloc is used

Previous by thread:
BlueTooth spewage

Next by thread:
Kext fails to load when falloc is used

Index(es):

Date
Thread