SSH to a server via Bastion - Revision history

Dbrownlee: /* Connecting to a server */

2025-08-13T14:15:45Z

Connecting to a server

← Older revision		Revision as of 14:15, 13 August 2025
Line 66:		Line 66:
	bssh <SERVER 2 USER>@<SERVER 2 IP>		bssh <SERVER 2 USER>@<SERVER 2 IP>
	</syntaxhighlight>OpenStack provides name resolution for VMs on the same network. If the Bastion server is on the same OpenStack network as the destination servers, you may use the VM name rather than its IP address. This makes using bssh essentially identical to using ssh (though rather than a destination domain name, the VM name is used). <syntaxhighlight lang="bash">		</syntaxhighlight>OpenStack provides name resolution for VMs on the same network. If the Bastion server is on the same OpenStack network as the destination servers, you may use the VM name rather than its IP address. This makes using bssh essentially identical to using ssh (though rather than a destination domain name, the VM name is used). <syntaxhighlight lang="bash">
	bssh <SERVER 1 USER>@<SERVER 1 ~~NAME~~>		bssh <SERVER 1 USER>@<SERVER 1 HOSTNAME>

	</syntaxhighlight>		</syntaxhighlight>

Dbrownlee: /* Typical Commands */

2025-08-11T15:52:54Z

Typical Commands

← Older revision		Revision as of 15:52, 11 August 2025
Line 74:		Line 74:
	# Show a help message, including available commands.		# Show a help message, including available commands.
	help		help
	# Basic info		# Basic info about your account.
	info		info
	# List accessible servers.		# List accessible servers.
	selfListAccess		selfListAccess
	# Generate scp passthrough script		# Generate scp passthrough script.
	scp		scp
	</syntaxhighlight>		</syntaxhighlight>
Line 89:		Line 89:
	BASTION_CMD="ssh davidbr@bastion-candig "		BASTION_CMD="ssh davidbr@bastion-candig "
	# Change to FQDN or IP address, if needed.		# Change to FQDN or IP address, if needed.
	BASTION_CMD="ssh davidbr@~~bastion~~.~~candig~~.~~sd4h~~.ca " # Or @<~~IP ADDRESS~~>		BASTION_CMD="ssh davidbr@198.168.188.147 " # Or @<DOMAIN NAME>
	</syntaxhighlight>The scp-via-bastion script may also be renamed (or aliased) and moved from $HOME to a directory within the user's $PATH (such as ~/.local/bin/).		</syntaxhighlight>The scp-via-bastion script may also be renamed (or aliased) and moved from $HOME to a directory within the user's $PATH (such as ~/.local/bin/).

	=== Access types ===		=== Access types ===
	The Bastion provides both Group and Personal access methodologies. Which method you use depends on The Bastion configurations. Your connections will work the same no matter which method is used, so from a user perspective, the distinction is moot.		The Bastion provides both Group and Personal access methodologies. Which method you use depends on The Bastion configurations. Your connections will work the same no matter which method is used, so from a user perspective, the distinction is moot.

Dbrownlee: /* Connecting to a server */

2025-08-11T14:55:30Z

Connecting to a server

← Older revision		Revision as of 14:55, 11 August 2025
Line 68:		Line 68:
	bssh <SERVER 1 USER>@<SERVER 1 NAME>		bssh <SERVER 1 USER>@<SERVER 1 NAME>

			</syntaxhighlight>

			=== Typical Commands ===
			The Bastion has a lot of commands available. Autocomplete is very helpful and removes the need to remember a whole new set of CLI commands. For a typical user, the [potentially] most relevant are: <syntaxhighlight lang="bash">
			# Show a help message, including available commands.
			help
			# Basic info
			info
			# List accessible servers.
			selfListAccess
			# Generate scp passthrough script
			scp
	</syntaxhighlight>		</syntaxhighlight>

Dbrownlee: /* Using scp, sftp, rsync through The Bastion */

2025-08-11T14:34:37Z

Using scp, sftp, rsync through The Bastion

← Older revision		Revision as of 14:34, 11 August 2025
Line 78:		Line 78:
	# Change to FQDN or IP address, if needed.		# Change to FQDN or IP address, if needed.
	BASTION_CMD="ssh davidbr@bastion.candig.sd4h.ca " # Or @<IP ADDRESS>		BASTION_CMD="ssh davidbr@bastion.candig.sd4h.ca " # Or @<IP ADDRESS>
	</syntaxhighlight>The scp-via-bastion script may also be renamed (or aliased) and moved from $HOME to a directory within the user's $PATH such as ~/.local/bin/.		</syntaxhighlight>The scp-via-bastion script may also be renamed (or aliased) and moved from $HOME to a directory within the user's $PATH (such as ~/.local/bin/).

	=== Access types ===		=== Access types ===
	The Bastion provides both Group and Personal access methodologies. Which method you use depends on The Bastion configurations. Your connections will work the same no matter which method is used, so from a user perspective, the distinction is moot.		The Bastion provides both Group and Personal access methodologies. Which method you use depends on The Bastion configurations. Your connections will work the same no matter which method is used, so from a user perspective, the distinction is moot.

Dbrownlee: /* Using scp, sftp, rsync through The Bastion */

2025-08-07T21:29:40Z

Using scp, sftp, rsync through The Bastion

← Older revision		Revision as of 21:29, 7 August 2025
Line 73:		Line 73:
	It is possible to scp files in both directions through The Bastion using a special script that The Bastion will generate for you. Follow the [https://ovh.github.io/the-bastion/plugins/open/scp.html scp setup directions] found in The Bastion documentation.		It is possible to scp files in both directions through The Bastion using a special script that The Bastion will generate for you. Follow the [https://ovh.github.io/the-bastion/plugins/open/scp.html scp setup directions] found in The Bastion documentation.

	~~The~~ scp-via-bastion script The Bastion generates ~~needs~~ some minor tweaking.		Check the scp-via-bastion script The Bastion generates - it may need some minor tweaking.<syntaxhighlight lang="bash">
	~~From:~~		# Check
	BASTION_CMD="ssh davidbr@bastion-candig "		BASTION_CMD="ssh davidbr@bastion-candig "
	~~To:~~		# Change to FQDN or IP address, if needed.
	BASTION_CMD="ssh davidbr@bastion.candig.sd4h.ca " # Or @<IP ADDRESS>		BASTION_CMD="ssh davidbr@bastion.candig.sd4h.ca " # Or @<IP ADDRESS>
	The scp-via-bastion script may also be renamed (or aliased) and moved to a directory ~~present in~~ the user's $PATH ~~rather than $HOME~~.		</syntaxhighlight>The scp-via-bastion script may also be renamed (or aliased) and moved from $HOME to a directory within the user's $PATH such as ~/.local/bin/.

	=== Access types ===		=== Access types ===
	The Bastion provides both Group and Personal access methodologies. Which method you use depends on The Bastion configurations. Your connections will work the same no matter which method is used, so from a user perspective, the distinction is moot.		The Bastion provides both Group and Personal access methodologies. Which method you use depends on The Bastion configurations. Your connections will work the same no matter which method is used, so from a user perspective, the distinction is moot.

Dbrownlee: /* Connection types */

2025-08-07T19:36:26Z

Connection types

← Older revision		Revision as of 19:36, 7 August 2025
Line 26:		Line 26:
	# Non-interactive mode		# Non-interactive mode
	# Directly to an external, registered server.		# Directly to an external, registered server.
	In a direct connection, ~~the bastion~~ acts as a transparent pass-through. This is the most convenient, likely and common way you will connect. See the "Connecting to a server" section below.		In a direct connection, The Bastion acts as a transparent pass-through. This is the most convenient, likely and common way you will connect. See the "Connecting to a server" section below.

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
Line 71:		Line 71:

	=== Using scp, sftp, rsync through The Bastion ===		=== Using scp, sftp, rsync through The Bastion ===
	~~More~~ to ~~follow~~.		It is possible to scp files in both directions through The Bastion using a special script that The Bastion will generate for you. Follow the [https://ovh.github.io/the-bastion/plugins/open/scp.html scp setup directions] found in The Bastion documentation.

			The scp-via-bastion script The Bastion generates needs some minor tweaking.
			From:
			BASTION_CMD="ssh davidbr@bastion-candig "
			To:
			BASTION_CMD="ssh davidbr@bastion.candig.sd4h.ca " # Or @<IP ADDRESS>
			The scp-via-bastion script may also be renamed (or aliased) and moved to a directory present in the user's $PATH rather than $HOME.

	=== Access types ===		=== Access types ===
	~~Coming soon!~~		The Bastion provides both Group and Personal access methodologies. Which method you use depends on The Bastion configurations. Your connections will work the same no matter which method is used, so from a user perspective, the distinction is moot.

	~~====~~ Group ~~====~~

	~~====~~ Personal ~~====~~

Dbrownlee: /* Bastion in a nutshell */

2025-08-07T18:48:10Z

Bastion in a nutshell

← Older revision		Revision as of 18:48, 7 August 2025
Line 1:		Line 1:
	== Bastion in a nutshell ==		== Bastion in a nutshell ==
	[https://ovh.github.io/the-bastion/index.html The Bastion] is a single point of entry for SSH connections.		[https://ovh.github.io/the-bastion/index.html The Bastion] is a single point of entry for SSH connections. Like an http reverse proxy for ssh, it is used to connect to other servers.

	Some servers in SD4H may not be publicly accessible from the public internet for security reasons.		Some servers in SD4H may not be publicly accessible from the public internet for security reasons.

Dbrownlee: /* Using scp, sftp, rsync */

2025-08-06T21:46:59Z

Using scp, sftp, rsync

← Older revision		Revision as of 21:46, 6 August 2025
Line 70:		Line 70:
	</syntaxhighlight>		</syntaxhighlight>

	=== Using scp, sftp, rsync ===		=== Using scp, sftp, rsync through The Bastion ===
	More to follow.		More to follow.

Dbrownlee at 21:46, 6 August 2025

2025-08-06T21:46:39Z

← Older revision		Revision as of 21:46, 6 August 2025
Line 69:		Line 69:

	</syntaxhighlight>		</syntaxhighlight>

			=== Using scp, sftp, rsync ===
			More to follow.

	=== Access types ===		=== Access types ===

Dbrownlee at 21:44, 6 August 2025

2025-08-06T21:44:57Z

← Older revision		Revision as of 21:44, 6 August 2025
Line 25:		Line 25:
	# Interactive mode		# Interactive mode
	# Non-interactive mode		# Non-interactive mode
	# Directly to a registered server.		# Directly to an external, registered server.
	In a direct connection, the bastion acts as a pass-through. This is the most convenient, likely and common way you will ~~use~~ connect. See the "Connecting to a server" section below.		In a direct connection, the bastion acts as a transparent pass-through. This is the most convenient, likely and common way you will connect. See the "Connecting to a server" section below.

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">