Networking Forums

Networking Forums > Computer Networking > Linux Networking > What happened after TCP failed retring sending

Reply
Thread Tools Display Modes

What happened after TCP failed retring sending

 
 
Steven Woody
Guest
Posts: n/a

 
      07-01-2008, 09:16 AM
Hi,

If two TCP stream socket opened on two different hosts connected ok,
then the network cable was cut off. One endpoint will in sometimes
write some data into its socket. Of course, these packets sent out
will not get any ACKs, my question is: in this case, will the socket
in the sending end noticed this kind of failure and close the socket
for the calling program? If so, how long will this happen?
(Supposing the keeep-alive option is off)

Thanks.

-
narke
 
Reply With Quote
 
 
 
 
David Schwartz
Guest
Posts: n/a

 
      07-01-2008, 10:12 AM
On Jul 1, 2:16*am, Steven Woody <narkewo...@gmail.com> wrote:
> Hi,
>
> If two TCP stream socket opened on two different hosts connected ok,
> then the network cable was cut off. *One endpoint will in sometimes
> write some data into its socket. *Of course, these packets sent out
> will not get any ACKs, my question is: in this case, will the socket
> in the sending end noticed this kind of failure and close the socket
> for the calling program? *If so, how long will this happen?
> (Supposing the keeep-alive option is off)


Yes, the error will be "send timed out" or its equivalent. The exact
amount of time depends upon the exact settings on each end, but 50
seconds to 4 minutes is typical.

Note that TCP does not guarantee that an end that does not send data
can detect a connection loss. The connection is only tested so long as
there is unacknowledged outbound data.

DS
 
Reply With Quote
 
Steven Woody
Guest
Posts: n/a

 
      07-03-2008, 05:37 AM
On Jul 1, 6:12 pm, David Schwartz <dav...@webmaster.com> wrote:
> On Jul 1, 2:16 am, Steven Woody <narkewo...@gmail.com> wrote:
>
> > Hi,

>
> > If two TCP stream socket opened on two different hosts connected ok,
> > then the network cable was cut off. One endpoint will in sometimes
> > write some data into its socket. Of course, these packets sent out
> > will not get any ACKs, my question is: in this case, will the socket
> > in the sending end noticed this kind of failure and close the socket
> > for the calling program? If so, how long will this happen?
> > (Supposing the keeep-alive option is off)

>
> Yes, the error will be "send timed out" or its equivalent. The exact
> amount of time depends upon the exact settings on each end, but 50
> seconds to 4 minutes is typical.
>
> Note that TCP does not guarantee that an end that does not send data
> can detect a connection loss. The connection is only tested so long as
> there is unacknowledged outbound data.
>
> DS


Thank you. I understood.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
I bet this has actually happened somewhere alexd Wireless Internet 2 04-25-2010 09:09 PM
I bet this has actually happened somewhere alexd Broadband 0 04-25-2010 04:58 PM
What happened? Scott H Wireless Networks 2 04-18-2007 02:56 AM
What happened to traceroute -I? Andrew Gideon Linux Networking 4 08-25-2006 12:23 AM
Help.... this must have happened to someone else John D O'Connor Windows Networking 2 03-03-2004 06:25 AM



1 2 3 4 5 6 7 8 9 10 11