DACHS/Login - Revision history

R Keller at 22:09, 26 February 2025

2025-02-26T22:09:46Z

← Older revision		Revision as of 00:09, 27 February 2025
Line 6:		Line 6:
	All home institutions of our current users are connected to BelWü, so if you are on your campus network (e.g. in your office or on the Campus WiFi) you should be able to connect to DACHS without restrictions.		All home institutions of our current users are connected to BelWü, so if you are on your campus network (e.g. in your office or on the Campus WiFi) you should be able to connect to DACHS without restrictions.
	If you are outside one of the BelWü networks (e.g. at home), a VPN connection to the home institution or a connection to an SSH jump host at the home institution must be established first.		If you are outside one of the BelWü networks (e.g. at home), a VPN connection to the home institution or a connection to an SSH jump host at the home institution must be established first.
			\|}

			{\|style="background:#deffee; width:100%;"
			\|style="padding:5px; background:#cef2e0; text-align:left"\|
			[[Image:Attention.svg\|center\|25px]]
			\|style="padding:5px; background:#cef2e0; text-align:left"\|
			VPN configured with [https://de.wikipedia.org/wiki/Split_Tunneling SPLIT tunneling mode] will '''not''' work, as any traffic not destined to your organizations IP range will not pass through your organizations VPN and hence will again be blocked by the Firewall.
	\|}		\|}

M Kunzelmann: add link to page to check whether the registered 2FA token works

2025-01-30T12:24:01Z

add link to page to check whether the registered 2FA token works

← Older revision		Revision as of 14:24, 30 January 2025
Line 174:		Line 174:
	== Troubleshooting ==		== Troubleshooting ==

			If your OTP code doesn't get accepted multiple times in a row, you should first check that the second factor works and is active in the [https://login.bwidm.de/user/twofa.xhtml bwIDM My Tokens section].
	Nothing yet.

	<!-- See [[BwUniCluster_2.0/FAQ#Login_Issues\|bwUniCluster FAQ]]. -->		<!-- See [[BwUniCluster_2.0/FAQ#Login_Issues\|bwUniCluster FAQ]]. -->


	= Allowed Activities on Login Nodes =		= Allowed Activities on Login Nodes =

M Kunzelmann: /* Hostnames */

2024-12-19T15:36:01Z

Hostnames

← Older revision		Revision as of 17:36, 19 December 2024
Line 89:		Line 89:


	If you explicitly connect to dachs-login1 but ~~wind~~ up on dachs-login2 (or the other way around), then of of them might not be available at the time and you're automatically redirected to the other one.		If you explicitly connect to dachs-login1 but end up on dachs-login2 (or the other way around), then of of them might not be available at the time and you're automatically redirected to the other one.

	== Host Keys ==		== Host Keys ==

M Kunzelmann: Adjust DNS login host selection

2024-12-19T15:35:21Z

Adjust DNS login host selection

← Older revision		Revision as of 17:35, 19 December 2024
Line 64:		Line 64:

	The system has two login nodes.		The system has two login nodes.
	The selection of the login node is done automatically. ~~(TODO. Needs to be implemented by RZ.)~~		The selection of the login node is done automatically.
	If you are logging in multiple times, different sessions might run on different login nodes.		If you are logging in multiple times, different sessions might run on different login nodes.

Line 77:		Line 77:

	In general, you should use automatic selection to allow us to balance the load over the two login nodes.		In general, you should use automatic selection to allow us to balance the load over the two login nodes.
	If you need to connect to specific login ~~nodes~~, you can use the following hostnames:		If you need to connect to specific login node, you can use the following hostnames:

	{\| class="wikitable"		{\| class="wikitable"
Line 87:		Line 87:
	\|-		\|-
	\|}		\|}


			If you explicitly connect to dachs-login1 but wind up on dachs-login2 (or the other way around), then of of them might not be available at the time and you're automatically redirected to the other one.

	== Host Keys ==		== Host Keys ==

M Kunzelmann: Set host keys

2024-12-19T15:23:12Z

Set host keys

← Older revision		Revision as of 17:23, 19 December 2024
Line 95:		Line 95:
	! Algorithm !! Fingerprint (SHA256)		! Algorithm !! Fingerprint (SHA256)
	\|-		\|-
	\| '''RSA''' \|\| SHA256:~~TODO~~		\| '''RSA''' \|\| SHA256:kdvbATXbd/ggG33G7VEw+O+FpJPcZU6XDeFyWXvBkhc
	\|-		\|-
	\| '''ECDSA''' \|\| SHA256:~~TODO~~		\| '''ECDSA''' \|\| SHA256:4Y/LvkPL9g9DZ8JrmTxXsMTIWyM/u/mEEmSB7S/2yyA
	\|-		\|-
	\| '''ED25519''' \|\| SHA256:~~TODO~~		\| '''ED25519''' \|\| SHA256:X9eRJepYD3da3BM1pgiWxnvRc/Pt5eBLUr18tDUsZjU
	\|-		\|-
	\|}		\|}

M Kunzelmann: Change link to queues to DACHS/Queues

2024-11-12T13:21:32Z

Change link to queues to DACHS/Queues

← Older revision		Revision as of 15:21, 12 November 2024
Line 194:		Line 194:
	* '''short''' pre- and post-processing of your batch jobs.		* '''short''' pre- and post-processing of your batch jobs.

			<!--
	TODO:		TODO:
	We advise users to use [[BwUniCluster_2.0_Batch_Queues#Interactive_Jobs\|interactive jobs]] for compute and memory intensive tasks like compiling.		We advise users to use [[BwUniCluster_2.0_Batch_Queues#Interactive_Jobs\|interactive jobs]] for compute and memory intensive tasks like compiling.
			-->

			We advise users to use [[DACHS/Queues\|interactive jobs]] for compute and memory intensive tasks like compiling.

	= Related Information =		= Related Information =

M Kunzelmann: adjust hostnames

2024-11-12T13:18:12Z

adjust hostnames

← Older revision		Revision as of 15:18, 12 November 2024
Line 160:		Line 160:

	<pre>		<pre>
	~ $ ssh -l es_vwxyz1234 login.hs-esslingen.de		~ $ ssh -l es_vwxyz1234 dachs-login.hs-esslingen.de
	(es_vwxyz1234@login.hs-esslingen.de) Your OTP: 123456		(es_vwxyz1234@dachs-login.hs-esslingen.de) Your OTP: 123456
	(es_vwxyz1234@login.hs-esslingen.de) Password:		(es_vwxyz1234@dachs-login.hs-esslingen.de) Password:
	********************************************************************************		********************************************************************************
	Last login: Thu Jul 7 18:09:43 2022 from login.hs-esslingen.de		Last login: Thu Jul 7 18:09:43 2022 from dachs-login.hs-esslingen.de
	********************************************************************************		********************************************************************************
	[es_vwxyz1234@login1 ~]$		[es_vwxyz1234@login1 ~]$

M Kunzelmann: comment Jupyterhub section

2024-11-12T13:16:18Z

comment Jupyterhub section

← Older revision		Revision as of 15:16, 12 November 2024
Line 134:		Line 134:
	'''Note:''' When using File transfer with MobaXterm version 23.6 the following configuration change has to be made:		'''Note:''' When using File transfer with MobaXterm version 23.6 the following configuration change has to be made:
	In the settings in the tab "SSH", change the option "SSH engine" from "<new>" to "<legacy>". Then restart MobaXterm		In the settings in the tab "SSH", change the option "SSH engine" from "<new>" to "<legacy>". Then restart MobaXterm

			<!-- TODO: We'll include this when we got Jupyterhub working.

	== Login with Jupyterhub ==		== Login with Jupyterhub ==
Line 146:		Line 148:
	More Information can be found [[BwUniCluster2.0/Jupyter#Login_process\|here]].		More Information can be found [[BwUniCluster2.0/Jupyter#Login_process\|here]].

			-->

	== Login Example ==		== Login Example ==

M Kunzelmann: adjust windows SSH login section

2024-11-12T13:15:28Z

adjust windows SSH login section

← Older revision		Revision as of 15:15, 12 November 2024
Line 125:		Line 125:
	Start ''MobaXterm'', fill in the following fields:		Start ''MobaXterm'', fill in the following fields:
	<pre>		<pre>
	Remote name : login.hs-esslingen.de		Remote name : dachs-login.hs-esslingen.de
	Specify user name : <username>		Specify user name : <username>
	Port : 22		Port : 22

M Kunzelmann: adjust SSH login section

2024-11-12T13:15:01Z

adjust SSH login section

← Older revision		Revision as of 15:15, 12 November 2024
Line 110:		Line 110:
	For login use one of the following ssh commands:		For login use one of the following ssh commands:

	ssh <username>@login.hs-esslingen.de		ssh <username>@dachs-login.hs-esslingen.de
	ssh -l <username> login.hs-esslingen.de		ssh -l <username> dachs-login.hs-esslingen.de


	TODO: Not sure if this will be available:

	To run graphical applications, you can use the <code>-X</code> or <code>-Y</code> flag to <code>ssh</code>:		To run graphical applications, you can use the <code>-X</code> or <code>-Y</code> flag to <code>ssh</code>:

	ssh -Y -l <username> login.hs-esslingen.de		ssh -Y -l <username> dachs-login.hs-esslingen.de

	For better performance, we recommend using [[VNC]].		For better performance, we recommend using [[VNC]].