we have been investigating the behaviour of the tcp retransmition timers
(rto) in relation with the irtt value given in the route command, and here
are the conclusions:
* The man page of "route" is wrong. The value of irtt is not in ms, but
in tens of ms. (1100 = 11 seconds)
* This irtt is used to set the initial value of rto (retransmition
timeout) during the tcp connexion phase, but rto and smothed round trip
time (srtt) are reseted to low values (too low for 1200 bauds) (-> Packet
acumulation in slow channels).
So, even if that "compatible" with the RFC, that's not very eficient for
slow packet radio. For me that's still a problem to do http connexions,
or access to servers with initial timeout timers (i.e inn), more if I use
Connected Mode (wich is the good way for me, has I am qrp and not very
well equiped (classic baycom modem, walky talky...)
I don't understand why this timers are reseted, nos flavours don't do it,
and that go much better. Is there a reason, or maybe that's a part of
the code which could be optimized ?
Thanks
-.-