using a mac with linux and filepro

[Bill Campbell]

On Mon, Jun 18, 2007, Jay R. Ashworth wrote:
>On Sat, Jun 16, 2007 at 03:26:17AM -0400, Fairlight wrote:
>> Now one thing I noticed was that certain protocols are REALLY dodgy about
>> this.  I noticed ssh in particular, if I actually lost sync, I could have
>> connections up to IRC or whatever, and as long as I recovered sync by the
>> end of the 2min timeout window on a connection, I regained that
>> connection for most TCP connections.  SSH, however, -never- survived a
>> DSL desync.  If that route goes away, *poof*, you are -gone-.  This is
>> both PuTTY and openssh.  Doesn't matter which.  Any versions...I've run
>> into it across more than a few versions of each.
>
>Keepalives.
>
>As long as your workstation maintains the same address, PuTTY/SSH will
>survive the intervening link going away.

That may depend on the type of connection, and whether there's activity on
the interface, particularly if the connection is from a local LAN behind a
NAT (Network Address Traslation) or IP masquerading firewall.

When our network was behind a Caldera OpenLinux 2.3 box doing IP
masquerading with ipchains, ssh connections would be broken after the tcp
timeout interval if there was no activity on the connection (I would often
run ``top'' on the remote machine to keep them active).  When we finally
replaced that box last year, moving to a SLES10 box using NAT with
iptables, the connections wouldn't time out when inactive.

My ssh connections have all been from Linux or OS X desktops so I can't
speak to what Windows does with putty, anzio, or other programs.

Bill
--
INTERNET:   bill at Celestial.COM  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
FAX:            (206) 232-9186  Mercer Island, WA 98040-0820; (206) 236-1676

Government is the great fiction, through which everbody endeavors to
live at the expense of everybody else.  -- Frederic Bastiat