lkml.org 
[lkml]   [1999]   [Nov]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Skyhigh retransmit times. Yearold problem still in 2.3.26
Date
Hello!

> > > 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?


Open your eyes! There is nothing to transmit here.
Retransmit timeout is bound to 120sec.

What's about these multihours times, it is keepalive timeout
(on2. It is really worth to blame to net-tools folks, my netstat show "ka")

Fix sshd not to enable this crap and enjoy with nice zero timer values.

Alexey Kuznetsov


-
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/

\
 
 \ /
  Last update: 2005-03-22 13:55    [W:0.780 / U:0.520 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site