Server/Client Alive mechanism issues
Jeff Mitchell
jmitchell at ll.mit.edu
Thu Jan 26 11:14:13 EST 2012
On 01/25/2012 06:49 PM, Ángel González wrote:
> On 25/01/12 23:06, Gert Doering wrote:
>> Hi,
>>
>> On Wed, Jan 25, 2012 at 12:26:34PM -0500, Jeff Mitchell wrote:
>>> My understanding is that since the alive mechanism is running inside the
>>> encrypted connection, OpenSSH would be able to (and would) prioritize
>>> the alive packets over other data. So if any data is able to get through
>>> (and it does) the alive packets should be able to as well. But this
>>> doesn't seem to be the case.
>> For that, OpenSSH would need to know that there is congestion, and
>> throttle it's send rate to avoid buffers building up *elsewhere*.
>>
>> If there is 10 seconds worth of data in your DSL router, there is nothing
>> OpenSSH can do to achieve a round-trip time of 1s for it's keepalives.
>>
>> gert
> Note that if you know the real bandwidth, you could use the --bwlimit
> parameter
> of rsync a little below that to not saturate it.
Good catch...I'll have to see if I can make the tool running rsync
accept custom parameters.
Thanks!
--Jeff
More information about the openssh-unix-dev
mailing list