0Ry5/netz39-infra-ansible
1
0
Fork 0
forked from Netz39_Admin/netz39-infra-ansible
Code Pull requests Activity
netz39-infra-ansible/templates/ssh_config.j2

36 lines
722 B
Text
Raw Permalink Normal View History

add a playbook to configure ssh to use the ssh gateway for the internal systems
2022-11-04 22:53:56 +01:00
# {{ ansible_managed }}
Host ssh.n39.eu
Hostname ssh.n39.eu
IdentityFile {{ setup_ssh_key }}
IdentitiesOnly yes
User {{ setup_ssh_logname }}
Port 22
:wrench: Clarify naming of ssh jump host groups The key difference between these groups is not that one needs a jump host and the other does not, but that all hosts of one group run on machines located in the Netz39 rooms in Magdeburg, while the other group contains only hosts hosted anywhere in the public internet. We'll need this distinction for more things than SSH in the future, e.g. PR !132. (This is also better, because technically there could be a third group requiring a jump host which is not ssh.n39.eu … :wink: ) Acked-by: Stefan Haun <tux@netz39.de> Acked-by: David Kilias <dkdent@netz39.de>
2023-01-09 21:09:43 +01:00
{% for host in groups['location_space'] %}
add a playbook to configure ssh to use the ssh gateway for the internal systems
2022-11-04 22:53:56 +01:00
Host {{ host }}
Hostname {{ host }}
IdentityFile {{ setup_ssh_key }}
IdentitiesOnly yes
User {{ setup_ssh_logname }}
ProxyJump ssh.n39.eu
Port 22
{% endfor %}
:wrench: Clarify naming of ssh jump host groups The key difference between these groups is not that one needs a jump host and the other does not, but that all hosts of one group run on machines located in the Netz39 rooms in Magdeburg, while the other group contains only hosts hosted anywhere in the public internet. We'll need this distinction for more things than SSH in the future, e.g. PR !132. (This is also better, because technically there could be a third group requiring a jump host which is not ssh.n39.eu … :wink: ) Acked-by: Stefan Haun <tux@netz39.de> Acked-by: David Kilias <dkdent@netz39.de>
2023-01-09 21:09:43 +01:00
{% for host in groups['location_internet'] %}
add a playbook to configure ssh to use the ssh gateway for the internal systems
2022-11-04 22:53:56 +01:00
Host {{ host }}
Hostname {{ host }}
IdentityFile {{ setup_ssh_key }}
IdentitiesOnly yes
User {{ setup_ssh_logname }}
Port 22
:wrench: Clarify naming of ssh jump host groups The key difference between these groups is not that one needs a jump host and the other does not, but that all hosts of one group run on machines located in the Netz39 rooms in Magdeburg, while the other group contains only hosts hosted anywhere in the public internet. We'll need this distinction for more things than SSH in the future, e.g. PR !132. (This is also better, because technically there could be a third group requiring a jump host which is not ssh.n39.eu … :wink: ) Acked-by: Stefan Haun <tux@netz39.de> Acked-by: David Kilias <dkdent@netz39.de>
2023-01-09 21:09:43 +01:00
{% endfor %}
Add SSH entry for host Rhodium Please note that it is still necessary to manually add the SSH keys to the OpenWRT config.
2025-01-12 12:55:56 +01:00
{# This is our router #}
Host rhodium.n39.eu
Hostname rhodium.n39.eu
IdentityFile {{ setup_ssh_key }}
User root
ProxyJump ssh.n39.eu
Port 22
Copy permalink