Messages in this thread | | | Date | Sun, 14 Nov 1999 13:15:24 +0000 | From | Steve Underwood <> | Subject | Re: Skyhigh retransmit times. Yearold problem still in 2.3.26 |
| |
Andi Kleen wrote:
> christoph@lameter.com (Christoph Lameter) writes: > > > I have been bitching about this for years .... > > > > This is for a ssh connection via a ricochet: > > > > netstat -ton > > > > tcp 0 0 127.0.0.1:1026 127.0.0.1:1027 ESTABLISHED off (0.00/0/0) > > tcp 0 0 204.179.131.123:1745 207.33.153.134:6667 ESTABLISHED on2 (7106.08/0/0) > > tcp 0 0 204.179.131.123:1023 207.33.153.134:22 ESTABLISHED on2 (6455.34/0/0) > > > > If there would at least be a command to reset those times to make the > > connection usable again.... This way I have to establish a new connection > > to the same host to do something usable. > > Once you get through again TCP will reset the timeouts itself as it > receives new ACKs.
Whilst this is true, I think many people would describe a protocol that allows 2 hour retransmits as broken. Were its designers looking for reasonable results on links between the Earth and Mars?
This is quite a pain with TCP across unreliable media (e.g. the Internet). A broken path gets fixed after some significant downtime, but established connections take an age to pick up again. There has be a Better Way.
Steve
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |