[twsocket] timeout when tcp connection on internet
Fri, 9 Jun 2000 22:02:35 +0200
I think my previous message was due to problems on 1 of the ISP's. Just a
few hours ago I read it in there news they had problem in one of there hops.
I tryed just to send a message to the same 'connected' line after more than
3 hours 'no traffic' and it seems to work ok. So obivoiusly there's no
timeout on a 'dead' tcp connection.
;-) strange, I ask a question and answer it myself ;-) I'm getting old I
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org]On
> Behalf Of Wilfried Mestdagh
> Sent: vrijdag 9 juni 2000 14:38
> To: TWSocket Mailing List
> Subject: [twsocket] timeout when tcp connection on internet
> I have a question about timeout when connected over internet. Situation is
> as follwos (TCP connection):
> LAN machine (client) -> cable modem -> ISP1 -> ISP2 -> router ->
> LAN machine
> When there is no traffic for a few hours both programs sockets
> are still in
> connected state, but if one of them is trying to send data it is
> never reach
> and the connection is broken after a few minutes. So
> I know I have to send keep-alive packets, but who does the
> timeout ? Is it
> the router, or something between the 2 internet providers ? If I run the
> same configuration on a LAN there seems not a timout.
> Does anybody know on what time interval I should send keep alive
> packets in
> sutch a situation ?
> Note that the machine connected with cable modem dus regulary gets dhcp
> messages (lease expired and renewed) but it does not seem that is
> the reason
> (trying to send immediatly after sutch a message does work).
> thanks in advance, Wilfried
> TWSocket mailing list [http://elists.org/mailman/listinfo/twsocket]
> Visit our website at http://www.rtfm.be/fpiette/indexuk.htm