Comments on: ssh with unstable and mobile clients

By: mirabilos

mirabilos — Wed, 25 Nov 2009 08:52:32 +0000

I now set a default timeout in MirBSD’s ssh and sshd of
200*3 seconds = 10 minutes, which I think is reasonable
as a generic default. (My P-233MMX server already has
been using a somewhat lower limit, but this will now be
the default for all installs of that OS.)

By: MJ Ray

MJ Ray — Mon, 23 Nov 2009 08:46:52 +0000

@Franklin – as you can see from the back-link, it started on planets, so it continues on planets.

@Aneurin Price – I’ll look into that required fields problem. It looks like the message which used to say which fields were required and other comments about comments has got lost in some upgrade. On the disconnects: OK, but if the client has gone dark for a few hours, it seems fair to stop wasting resources on them.

By: Aneurin Price

Aneurin Price — Sun, 22 Nov 2009 11:25:10 +0000

Your blog software doesn’t specify which fields are required, then produces an error page if they are not filled in, from which the only recourse is to click ‘back’ and discover that the contents of the comment box have been mysteriously eaten.

Short recap: turning on keepalives in situations of discontinuous network connectivity causes TCP sessions to terminate when they otherwise might have remained open until the connection is resumed, if only you had not tried to send data down them.

By: mirabilos

mirabilos — Sat, 21 Nov 2009 15:38:48 +0000

Ad 1: I don’t think so, I use both on my server and also wonder why these aren’t enabled by default. (I’d be interested in any reasoning on this, too.)

By: Franklin

Franklin — Sat, 21 Nov 2009 14:00:34 +0000

Turning DebianPlanet into a support tool?
(Why not using debian-user mailing list ?)