Another ssh problem - it looks up after a couple of minutes.
From: Dave (nospam_at_nowhere.com)
Date: 08/28/05
- Previous message: Dimitri Maziuk: "Re: problems regarding "This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin""
- Next in thread: Laurent Blume: "Re: Another ssh problem - it looks up after a couple of minutes."
- Reply: Laurent Blume: "Re: Another ssh problem - it looks up after a couple of minutes."
- Reply: Oscar del Rio: "Re: Another ssh problem - it looks up after a couple of minutes."
- Reply: Michael Laajanen: "Re: Another ssh problem - it looks up after a couple of minutes."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 28 Aug 2005 14:15:24 +0100
This is nothing to do with the problem I mentioned before of ssh -X not
working on Sun related newsgroups - its another problem entirely.
I have a Sun Ultra 80 running Solaris 9 and ssh version (Sun_SSH_1.0)
which is based on some variant of OpenSSH.
Whenever I connect to another machine that has ssh running (including
other Suns with other non-OpenSSH based servers), the connection locks
up after a minute or two if not used. If its used, it keeps working.
Any ideas what might be causing it to lock up if not used for a couple
of minutes?
What I've tried/considered
1) I can't see any timeouts mentioned, other than
LoginGraceTime 600
in the sshd_config file of either machine.
2) KeepAlive yes
is set in the /etc/ssh/ssh_config file
(I'm not sure if that an OpenSSH command or not, but it is available on
Suns).
3) I normally use tcsh, but have set up an accounts at both ends with
/usr/local/bin/bash, and it still locks up.
4) I do allow direct root logins on one machine (yes I know it has its
security risks) and it happens if logging in as root (/bin/sh, which is
not the same as bash on a Sun) or as a normal user with /bin/tcsh
5) The local host has a firewall in the ADSL modem/router, but the
timeout has been set >> than the time before the thing locks up.
In one case, where a machine is on my local subnet, there is no firewall
on that. In the other case, when I connect to my employers network,
there is a firewall, but I have no idea how it is configured. But I had
the problem long before there was any firewall there.
6) I've had the problem for years, despite shells, versions of the OS,
versions of SSH, hardware, firewalls all changing over the period. The
only thing that is common is Sun hardware at both ends.
7) I normally use vi, but it happens if inside vi, or just as the
command prompts.
I've just thought of trying to run an X terminal on the remote machine,
putting that into the background, and having a loop the prints the date
every minute. I've not tried that one, but that is at best a poor hack
even if it does work.
Any idea??
- Previous message: Dimitri Maziuk: "Re: problems regarding "This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin""
- Next in thread: Laurent Blume: "Re: Another ssh problem - it looks up after a couple of minutes."
- Reply: Laurent Blume: "Re: Another ssh problem - it looks up after a couple of minutes."
- Reply: Oscar del Rio: "Re: Another ssh problem - it looks up after a couple of minutes."
- Reply: Michael Laajanen: "Re: Another ssh problem - it looks up after a couple of minutes."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|