TCP reconnect after network cable disconnect.

On Aug 27, 1:11 am, gNash <ganeshamu....DeleteThis@gmail.com> wrote:

> Please help me how to resume the connection. after cable broken or
> time out ?

The connection should resume all by itself. There should be nothing
special you need to do. What goes wrong?

DS

On Aug 30, 11:17 pm, David Schwartz <dav....RemoveThis@webmaster.com> wrote:
> On Aug 27, 1:11 am, gNash <ganeshamu....RemoveThis@gmail.com> wrote:
>
> > Please help me how to resume the connection. after cable broken or
> > time out ?
>
> The connection should resume all by itself. There should be nothing
> special you need to do. What goes wrong?
>
> DS

This same thing happen to me on my Ubuntu install. It does not matter
what if command I use, up/down, the only way I could go back online is
if I reboot. Strange.

On Sep 1, 6:09 am, nestwasright <nestami... RemoveThis @gmail.com> wrote:

> This same thing happen to me on my Ubuntu install. It does not matter
> what if command I use, up/down, the only way I could go back online is
> if I reboot. Strange.

What is the symptom exactly? Is the interface up? Can you ping your
gateway?

DS

In article <374b1c71-52d0-46a0-b150-120b94c4f93f.DeleteThis@p10g2000prm.googlegroups.com>,
gNash <ganeshamutha.DeleteThis@gmail.com> wrote:
>I am writing some application like file download through HTTP
>protocol.
>
> The application downloading file very fine as along as there was no
>disruption network cable.
>
>But when cable disrupting events like unplug and plug after some time,
>i could not receive data.
>i am using timed out mechanism to avoid blocking in recv() or send().
>i was receiving errno as EWOULDBLOCK but i ignored it and keep on
>receiving to proceed download further.

You might check if you have TCP Keepalives switched on. If you have, switch
them off, if you want your connection to survive network outages.

>i have few more doubts :
>i) i could observe the network time out error only once. but each recv
>() expected to be returned time out error. is not it?

As far as I can see you should get the ETIMEDOUT only once per timeout
event.

>ii) After plugging the network cable there was no indication for data
>receive.

TCP retransmission times can be very long. You should wait at least as long
as the cable was unplugged if you want to test if your connection does
resume.

I hope this helps. Please post your result to the group.

cu

AW
--
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Arne Wichmann (aw@linux.de)

Arne Wichmann <aw.DeleteThis@old-forest.org> wrote:
> You might check if you have TCP Keepalives switched on. If you have,
> switch them off, if you want your connection to survive network
> outages.

.... when there isn't data being actively transferred across the
connection. If the cable disconnect/reconnect tests are happening
while there is activity on the connection, TCP Keepalives on/off won't
matter.

rick jones
--
No need to believe in either side, or any side. There is no cause.
There's only yourself. The belief is in your own precision. - Joubert
these opinions are mine, all mine; HP might not want them anyway...
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...