Reverse SSH Tunnel - Revision history

Leo at 16:27, 15 June 2023

2023-06-15T16:27:21Z

← Older revision		Revision as of 16:27, 15 June 2023
Line 23:		Line 23:

	=== SSH reverse tunnel with Systemd ===		=== SSH reverse tunnel with Systemd ===
	I use the following reverse SSH tunnel service file ~~that connects back to my machine at home and allows me~~ to SSH ~~via localhost:42069 to connect back~~. This is useful if the server you're working on is behind half a dozen firewalls.		I use the following reverse SSH tunnel service file to start the SSH reverse tunnel. This is useful if the server you're working on is behind half a dozen firewalls. Make sure to change the path to the private key, the desired tunnel port, and the server.

	{{Highlight		{{Highlight
	\| code = [Unit]		\| code = # cat <<EOF >/etc/systemd/system/ssh-reverse.service
			[Unit]
	Description=SSH Reverse Tunnel		Description=SSH Reverse Tunnel
	After=network-online.target		After=network-online.target
Line 40:		Line 42:
	[Install]		[Install]
	WantedBy=multi-user.target		WantedBy=multi-user.target
			EOF
			# systemctl daemon-reload
			# systemctl start ssh-reverse
			# systemctl enable ssh-reverse
	\| lang = terminal		\| lang = terminal
	}}		}}
	Install the service file to <code>/etc/systemd/system/ssh-reverse.sh</code>, then run <code>systemctl daemon-reload</code>, <code>systemctl start ssh-reverse</code>, <code>systemctl enable ssh-reverse</code>.{{Navbox Linux}}
			{{Navbox Linux}}
	[[Category:Linux]]		[[Category:Linux]]

Leo at 22:19, 29 April 2022

2022-04-29T22:19:29Z

@@ Line 1: / Line 1: @@
 Read more about [[SSH#Tunnels|other types of SSH tunnels]].
 Suppose you are inside a network that has no public IP address. If you are working on machineA, and you need to SSH in from outside the network, say from machineB, run the following on machineA:
@@ Line 21: / Line 22: @@
 }}
-{{Navbox Linux}}
+=== SSH reverse tunnel with Systemd ===
 [[Category:Linux]]

Leo at 00:16, 11 March 2021

2021-03-11T00:16:49Z

← Older revision		Revision as of 00:16, 11 March 2021
Line 1:		Line 1:
			Read more about [[SSH#Tunnels\|other types of SSH tunnels]].

	Suppose you are inside a network that has no public IP address. If you are working on machineA, and you need to SSH in from outside the network, say from machineB, run the following on machineA:		Suppose you are inside a network that has no public IP address. If you are working on machineA, and you need to SSH in from outside the network, say from machineB, run the following on machineA:

Line 10:		Line 12:
	}}		}}

	The first command creates a SSH tunnel which will listen on 127.0.0.1:22222 on machineB that tunnels to localhost:22 on machineA. You should now be able to access machineB:22 by connecting to 127.0.0.1:22222 on machineA.		The first command creates a SSH tunnel which will listen on <code>127.0.0.1:22222</code> on machineB that tunnels to <code>localhost:22</code> on machineA. You should now be able to access <code>machineB:22</code> by connecting to <code>127.0.0.1:22222</code> on machineA.

	You can make the tunnel target a remote host by replacing {{code\|localhost}} with another server.		You can make the tunnel target a remote host by replacing {{code\|localhost}} with another server.
Line 19:		Line 21:
	}}		}}

	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}
			[[Category:Linux]]

Leo at 17:49, 4 November 2019

2019-11-04T17:49:26Z

← Older revision		Revision as of 17:49, 4 November 2019
Line 14:		Line 14:
	You can make the tunnel target a remote host by replacing {{code\|localhost}} with another server.		You can make the tunnel target a remote host by replacing {{code\|localhost}} with another server.

	You may make the tunnel bind on all addresses instead of {{code\|127.0.0.1}} by ensuring that {{code\|GatewayPorts = yes}} or {{code\|GatewayPorts = clientspecified}} on machineB's SSH server and then specifying the bind address when connecting. Eg.		You may make the tunnel bind on all addresses instead of {{code\|127.0.0.1}} by ensuring that {{code\|1=GatewayPorts = yes}} or {{code\|1=GatewayPorts = clientspecified}} on machineB's SSH server and then specifying the bind address when connecting. Eg.
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	machineA$ ssh -R 0.0.0.0:22222:localhost:22 user@machineB		machineA$ ssh -R 0.0.0.0:22222:localhost:22 user@machineB

Leo at 17:42, 4 November 2019

2019-11-04T17:42:39Z

← Older revision		Revision as of 17:42, 4 November 2019
Line 1:		Line 1:
	Suppose you are inside a network that has no public IP address. If you are working on machineA, and you need to SSH in from outside the network, say from machineB, run the following on machineA:		Suppose you are inside a network that has no public IP address. If you are working on machineA, and you need to SSH in from outside the network, say from machineB, run the following on machineA:

	machineA$ ssh -R 22222:localhost:22 user@machineB		{{highlight\|lang=terminal\|code=
			machineA$ ssh -R 22222:localhost:22 user@machineB
			}}

	On machineB, you can now SSH to machineA by running:		On machineB, you can now SSH to machineA by running:
			{{highlight\|lang=terminal\|code=
			machineB$ ssh user@localhost -p 22222
			}}

	machineB~~$ ssh user@localhost -p~~ 22222		The first command creates a SSH tunnel which will listen on 127.0.0.1:22222 on machineB that tunnels to localhost:22 on machineA. You should now be able to access machineB:22 by connecting to 127.0.0.1:22222 on machineA.

	~~The first command creates~~ a ~~SSH tunnel which opens port 22222 on machineB that tunnels to machineA:22. You may extend this~~ by replacing localhost with another ~~host~~ on the ~~internal network in order to SSH in remotely to another host~~.		You can make the tunnel target a remote host by replacing {{code\|localhost}} with another server.

			You may make the tunnel bind on all addresses instead of {{code\|127.0.0.1}} by ensuring that {{code\|GatewayPorts = yes}} or {{code\|GatewayPorts = clientspecified}} on machineB's SSH server and then specifying the bind address when connecting. Eg.
			{{highlight\|lang=terminal\|code=
			machineA$ ssh -R 0.0.0.0:22222:localhost:22 user@machineB
			}}

	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]

Leo: Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

2019-09-01T06:21:03Z

Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

← Older revision		Revision as of 06:21, 1 September 2019
Line 9:		Line 9:
	The first command creates a SSH tunnel which opens port 22222 on machineB that tunnels to machineA:22. You may extend this by replacing localhost with another host on the internal network in order to SSH in remotely to another host.		The first command creates a SSH tunnel which opens port 22222 on machineB that tunnels to machineA:22. You may extend this by replacing localhost with another host on the internal network in order to SSH in remotely to another host.

	[[Category:Linux]]~~{{Navbox Linux}}~~		{{Navbox Linux}}[[Category:Linux]]

Leo: Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

2019-09-01T05:08:36Z

Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

← Older revision		Revision as of 05:08, 1 September 2019
Line 9:		Line 9:
	The first command creates a SSH tunnel which opens port 22222 on machineB that tunnels to machineA:22. You may extend this by replacing localhost with another host on the internal network in order to SSH in remotely to another host.		The first command creates a SSH tunnel which opens port 22222 on machineB that tunnels to machineA:22. You may extend this by replacing localhost with another host on the internal network in order to SSH in remotely to another host.

	[[Category:Linux]]		[[Category:Linux]]{{Navbox Linux}}

136.159.16.240: Created page with "Suppose you are inside a network that has no public IP address. If you are working on machineA, and you need to SSH in from outside the network, say from machineB, run the fol..."

2015-03-02T23:19:04Z

Created page with "Suppose you are inside a network that has no public IP address. If you are working on machineA, and you need to SSH in from outside the network, say from machineB, run the fol..."

New page

Suppose you are inside a network that has no public IP address. If you are working on machineA, and you need to SSH in from outside the network, say from machineB, run the following on machineA:

machineA$ ssh -R 22222:localhost:22 user@machineB

On machineB, you can now SSH to machineA by running:

machineB$ ssh user@localhost -p 22222

The first command creates a SSH tunnel which opens port 22222 on machineB that tunnels to machineA:22. You may extend this by replacing localhost with another host on the internal network in order to SSH in remotely to another host.

[[Category:Linux]]