SSH Timeouts - Revision history

Steve410 at 12:58, 15 March 2024

2024-03-15T12:58:46Z

Steve410: /* Using tmux Or screen As An Alternative */

2020-01-09T15:18:02Z

Using tmux Or screen As An Alternative

Steve410 at 15:17, 9 January 2020

2020-01-09T15:17:02Z

Steve410 at 15:16, 9 January 2020

2020-01-09T15:16:00Z

Steve410: /* Configure an OpenSSH Client To Prevent SSH Timeouts */

2020-01-09T15:15:21Z

Configure an OpenSSH Client To Prevent SSH Timeouts

Steve410 at 15:14, 9 January 2020

2020-01-09T15:14:56Z

Steve410: /* Configure an OpenSSH Client To Prevent SSH Timeouts */

2020-01-09T15:05:58Z

Configure an OpenSSH Client To Prevent SSH Timeouts

Steve410: /* Configure an OpenSSH Client To Prevent SSH Timeouts */

2020-01-09T14:51:20Z

Configure an OpenSSH Client To Prevent SSH Timeouts

Steve410 at 14:50, 9 January 2020

2020-01-09T14:50:52Z

Steve410: Created page with " Due to the various ssh programs people use to connect to servers, their configuration processes differ, so we cannot tell you how to set up your specific ssh client program..."

2020-01-09T14:37:23Z

Created page with " Due to the various ssh programs people use to connect to servers, their configuration processes differ, so we cannot tell you how to set up your specific ssh client program..."

New page

Due to the various ssh programs people use to connect to servers, their configuration processes differ, so we cannot tell you how to set up your specific ssh client program.

However, if you use '''OpenSSH''' to connect to a Linux system , you should add the following three lines do your ''~/.ssh/config'' file.

:: Host *
:: ClientAliveInterval 20
:: ClientAliveCountMax 5

'''NOTE:''' these lines will apply to '''''every''''' system you connect to. You'd have to use a more specific Host line in order tosingle out just the CS Linux systems.

==Using ''tmux'' Or ''screen'' As An Alternative==

One thing many people do for long-running programs is to run them inside a
'''tmux''' or '''screen''' session. That allows the programs to continue even if the SSH session is disconnected.

If you do this, '''''make sure you do come back
to check on your programs!''''' Sometimes, people forget about their running
programs and leave them, unnecessarily using up computing resources that
should be available for other people using our services.

You can learn more about tmux here: [https://tmux.github.io/ https://tmux.github.io/]

[[Linux Clients]]
[[Category:Troubleshooting]]

← Older revision		Revision as of 12:58, 15 March 2024
Line 34:		Line 34:


−	[[Category: ~~Linux Clients~~]]	+	[[Category:SSH]]
	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]

@@ Line 26: / Line 26: @@
 ==Using ''tmux'' Or ''screen'' As An Alternative==
-:One thing many people do for long-running programs is to run them inside a
+:One thing many people do for long-running programs is to run them inside a '''tmux''' or '''screen''' session.  That allows the programs to continue even if the SSH session is disconnected.
-:If you do this, '''''make sure you do come back
+:If you do this, '''''make sure you do come back to check on your programs!''''' Sometimes, people forget about their runningprograms and leave them, unnecessarily using up computing resources that should be available for other people using our services.
 : You can learn more about tmux here: [https://tmux.github.io/ https://tmux.github.io/]

@@ Line 1: / Line 1: @@
-Some users might experience a timeout/disconnect after being logged into a system using ssh for some period of time of non-direct activity. For example, you might be logged into one of our Linux systems via ssh, and you might start up a process that is expected to take a long time to run.  However, with no keyboard activity for a while while your process is running, ssh may time out and disconnect your session.
+:Some users might experience a timeout/disconnect after being logged into a system using ssh for some period of time of non-direct activity. For example, you might be logged into one of our Linux systems via ssh, and you might start up a process that is expected to take a long time to run.  However, with no keyboard activity for a while while your process is running, ssh may time out and disconnect your session.
-Sometimes, firewalls (and other network characteristics) in-between your client and a server may affect ssh connection times.  In other instances, there are settings you can make with your ssh client that might help prevent timeouts.
+:Sometimes, firewalls (and other network characteristics) in-between your client and a server may affect ssh connection times.  In other instances, there are settings you can make with your ssh client that might help prevent timeouts.
-So, settings to prevent ssh timeouts should be set ''at the client end'', meaning, the system you're using to connect to a remote system.
+:So, settings to prevent ssh timeouts should be set ''at the client end'', meaning, the system you're using to connect to a remote system.
-Due to the various ssh client programs people use to connect to servers, their configuration processes differ, so we cannot tell you how to set up your specific ssh client program.  But, we can provide you some info if you run an OpenSSH client, just like our own CS Linux clients use...
+:Due to the various ssh client programs people use to connect to servers, their configuration processes differ, so we cannot tell you how to set up your specific ssh client program.  But, we can provide you some info if you run an OpenSSH client, just like our own CS Linux clients use...
 == Configure an ''OpenSSH'' Client To Prevent SSH Timeouts==
-If you use '''OpenSSH''' to connect to a remote Linux system, on the system you're coming ''from'', you could consider adding lines ''similar'' to the following three lines to your ''~/.ssh/config'' file to help prevent SSH timeouts:
+:If you use '''OpenSSH''' to connect to a remote Linux system, on the system you're coming ''from'', you could consider adding lines ''similar'' to the following three lines to your ''~/.ssh/config'' file to help prevent SSH timeouts:
 :: Host *
@@ Line 16: / Line 16: @@
 :: ServerAliveCountMax 5
-In this example, for '''all''' hosts you connect to, if the client (your system) has not received anything for 20 seconds, your client will send an "invisible packet" to keep the connection alive.  If your client sends 5 keepalive packets in a row without acknowledgement from the server, your client will close the connection.
+:In this example, for '''all''' hosts you connect to, if the client (your system) has not received anything for 20 seconds, your client will send an "invisible packet" to keep the connection alive.  If your client sends 5 keepalive packets in a row without acknowledgement from the server, your client will close the connection.
-But, don't make your numbers too large or too small due to the way firewalls and the network handle the traffic.  The above is just an example.  You'd have to fine tune your configuration for your network environment.
+:But, don't make your numbers too large or too small due to the way firewalls and the network handle the traffic.  The above is just an example.  You'd have to fine tune your configuration for your network environment.
-Please see your OpenSSH client's ssh_config(5) man page for additional options  and more in-depth info about the above config lines.
+:Please see your OpenSSH client's ssh_config(5) man page for additional options  and more in-depth info about the above config lines.
-'''NOTE:'''  if you add lines like the above to your ssh config file, due to the '''Host *''' line, these lines would apply to '''''every''''' system you connect to from your OpenSSH client.  You'd have to use a more specific ''Host'' line in order to single out just the CS Linux systems.
+::'''NOTE:'''  if you add lines like the above to your ssh config file, due to the '''Host *''' line, these lines would apply to '''''every''''' system you connect to from your OpenSSH client.  You'd have to use a more specific ''Host'' line in order to single out just the CS Linux systems.
 ==Using ''tmux'' Or ''screen'' As An Alternative==
-One thing many people do for long-running programs is to run them inside a
+:One thing many people do for long-running programs is to run them inside a
 '''tmux''' or '''screen''' session.  That allows the programs to continue even if the SSH session is disconnected.
-If you do this, '''''make sure you do come back
+:If you do this, '''''make sure you do come back
 to check on your programs!''''' Sometimes, people forget about their running
 programs and leave them, unnecessarily using up computing resources that
 should be available for other people using our services.
-You can learn more about tmux here: [https://tmux.github.io/ https://tmux.github.io/]
+: You can learn more about tmux here: [https://tmux.github.io/ https://tmux.github.io/]

← Older revision		Revision as of 15:16, 9 January 2020
Line 38:		Line 38:


−	[[Linux Clients]]	+	[[Category: Linux Clients]]
	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]

@@ Line 10: / Line 10: @@
 == Configure an ''OpenSSH'' Client To Prevent SSH Timeouts==
-If you use '''OpenSSH''' to connect to a remote Linux system, on the system you're coming ''from'', you could consider adding lines similar to the following three lines to your ''~/.ssh/config'' file to help prevent SSH timeouts:
+If you use '''OpenSSH''' to connect to a remote Linux system, on the system you're coming ''from'', you could consider adding lines ''similar'' to the following three lines to your ''~/.ssh/config'' file to help prevent SSH timeouts:
 :: Host *

@@ Line 8: / Line 8: @@
 == Configure an ''OpenSSH'' Client To Prevent SSH Timeouts==
-If you use '''OpenSSH''' to connect to a remote Linux system, on the system you're coming ''from'', you should add the following three lines do your ''~/.ssh/config'' file to help prevent SSH timeouts:
+If you use '''OpenSSH''' to connect to a remote Linux system, on the system you're coming ''from'', you could consider add the lines similar to the following three lines do your ''~/.ssh/config'' file to help prevent SSH timeouts:
 :: Host *
-:: ClientAliveInterval 20
+:: ServerAliveInterval 20
-:: ClientAliveCountMax 5
+:: ServerAliveCountMax 5

@@ Line 1: / Line 1: @@
-Due to the various ssh programs people use to connect to servers, their configuration processes differ, so we cannot tell you how to set up your specific ssh client program.
+Due to the various ssh programs people use to connect to servers, their configuration processes differ, so we cannot tell you how to set up your specific ssh client program.  But, we can provide you some info if you run an OpenSSH client, just like our own CS Linux clients use...
-However, if you use '''OpenSSH''' to connect to a Linux system , you should add the following three lines do your ''~/.ssh/config'' file.
+== Configure an ''OpenSSH'' Client To Prevent SSH Timeouts==
 :: Host *
@@ Line 11: / Line 15: @@
-'''NOTE:'''  these lines will apply to '''''every''''' system you connect to.  You'd have to use a more specific Host line in order tosingle out just the CS Linux systems.
+'''NOTE:'''  these lines will apply to '''''every''''' system you connect to from your OpenSSH client.  You'd have to use a more specific ''Host'' line in order to single out just the CS Linux systems.
 ==Using ''tmux'' Or ''screen'' As An Alternative==