Linux/SSH - Revision history

Admin at 22:04, 25 March 2017

2017-03-25T22:04:16Z

2016-03-13T06:49:10Z

References

2016-03-13T06:47:43Z

user

@@ Line 94: / Line 94: @@
 /etc/ssh/ssh_config - just config for clients
 /etc/ssh/ssh_config - config for everything\
 </pre>

2016-03-13T06:44:37Z

SSH configuration

← Older revision		Revision as of 06:44, 13 March 2016
Line 48:		Line 48:

	You can configure ssh by editing system-wide configuration files (affects everyone) or user-specific files (affect only you).		You can configure ssh by editing system-wide configuration files (affects everyone) or user-specific files (affect only you).

			==User-specific ssh configuration==

	User specific configuration file for ssh is located in <code>~/.ssh/config</code>		User specific configuration file for ssh is located in <code>~/.ssh/config</code>
Line 77:		Line 79:
	</pre>		</pre>

			to set keep alive interval for all hosts:

			<pre>
			Host *
			ServerAliveInterval 60
			</pre>


			==System ssh configuration==

			To change ssh config for whole system, use files at

			<pre>
			/etc/ssh/ssh_config - just config for clients
			/etc/ssh/ssh_config - config for everything\
			</pre>

	=References=		=References=

2016-03-13T06:42:10Z

References

← Older revision		Revision as of 06:42, 13 March 2016
Line 44:		Line 44:

	Now port localhost:8001 on the remote machine will forward to 10.5.5.2:8000		Now port localhost:8001 on the remote machine will forward to 10.5.5.2:8000

			=SSH configuration=

			You can configure ssh by editing system-wide configuration files (affects everyone) or user-specific files (affect only you).

			User specific configuration file for ssh is located in <code>~/.ssh/config</code>

			Example of file defining several hosts with fixed IP addresses:

			<pre>
			Host dummy
			Hostname 4.4.4.4
			Port 22
			User foobar

			Host dada
			Hostname 120.120.120.150
			Port 20
			User stein
			</pre>

			These entries can be modified to add a server alive interval, which specifies an interval at which to send a keep alive packet to keep your connection alive.

			Example modification:

			<pre>
			Host dummy
			ServerAliveInterval 60
			Hostname 4.4.4.4
			Port 22
			User foobar
			</pre>




	=References=		=References=

2016-03-13T06:36:33Z

Create ssh tunnel

@@ Line 24: / Line 24: @@
 ssh -L 8001:localhost:8000 username@10.1.1.101
 </pre>
 =References=

2016-03-13T06:00:32Z

Create ssh tunnel

← Older revision		Revision as of 06:00, 13 March 2016
Line 16:		Line 16:

	From the client, you'll connect to the server with the ssh command, but with some additional flags that create the SSH tunnel: <code>ssh -L <local-port>:localhost:<remote-port> username@10.1.1.101</code>		From the client, you'll connect to the server with the ssh command, but with some additional flags that create the SSH tunnel: <code>ssh -L <local-port>:localhost:<remote-port> username@10.1.1.101</code>

			Here is what the syntax means:

			to forward port 8001 on my local machine, the client, to port 8000 on the remote machine, the server, at IP address 10.1.1.101, I will run the following ssh command:

			<pre>
			ssh -L 8001:localhost:8000 username@10.1.1.101
			</pre>

	=References=		=References=

2016-03-13T05:58:13Z

SSH for Linux Tasks

← Older revision		Revision as of 05:58, 13 March 2016
Line 1:		Line 1:
	=SSH for Linux Tasks=		=SSH for Linux Tasks=

			many useful tasks that can be done over SSH. unfortunately, most windoze networks block port 22.

			=SSH tunnels=

	Mostly stuff we already know - but you can build ssh tunnels. This allows you to access services locally that originate from another computer or server.		Mostly stuff we already know - but you can build ssh tunnels. This allows you to access services locally that originate from another computer or server.
Line 6:		Line 10:

	It also allows you to access servers on a private network, from a remote location.		It also allows you to access servers on a private network, from a remote location.

			==Create ssh tunnel==

	You need ssh on both the client and server side. You'll run an SSH server on the server side, and connect to it with an SSH client on the client side.		You need ssh on both the client and server side. You'll run an SSH server on the server side, and connect to it with an SSH client on the client side.

2016-03-13T05:57:02Z

SSH for Linux Tasks

← Older revision		Revision as of 05:57, 13 March 2016
Line 1:		Line 1:
	=SSH for Linux Tasks=		=SSH for Linux Tasks=

			Mostly stuff we already know - but you can build ssh tunnels. This allows you to access services locally that originate from another computer or server.

			This capability enables you to bypass local DNS filtering (by routing DNS queries through the SSH tunnel instead of to the network's default DNS).

			It also allows you to access servers on a private network, from a remote location.

			You need ssh on both the client and server side. You'll run an SSH server on the server side, and connect to it with an SSH client on the client side.

			From the client, you'll connect to the server with the ssh command, but with some additional flags that create the SSH tunnel: <code>ssh -L <local-port>:localhost:<remote-port> username@10.1.1.101</code>

	=References=		=References=

2016-03-13T05:50:24Z

Created page with "=SSH for Linux Tasks= =References= "Mastering Linux" {{SSHFlag}} {{NetworkingFlag}}"

New page

=SSH for Linux Tasks=

=References=

"Mastering Linux"

{{SSHFlag}}
{{NetworkingFlag}}