For users connecting from machines with a globally routed IPv6 address assigned to them, their SSH clients will favor IPv6. This can lead to issues for users who have uploaded SSH public keys with `from=` clauses based solely on IPv4 addresses or using patterns based on host names that do not match the host names their internet provider assigns to IPv6 addresses.
The long-term solution for these issues is to update your `from=` clauses to include patterns based on IPv6 addresses (or hostnames matching the IPv6 addresses).
A short-term solution can be to revert to IPv4 connectivity. This can be done by connecting to a new DNS name which will keep resolving to IPv4 addresses only: `jureca-ipv4.fz-juelich.de`. Another option is to disallow IPv6 in your SSH client. For OpenSSH, this can be done with the command line option `-4` or the configuration setting `AddressFamily inet`. In PuTTY the protocol can be overridden with the setting '_Internet protocol version_' in the '_Connection_' pane.
The `-X` option in the ssh-command enables "X11 forwarding"; this allows you to forward the graphical output of the X graphics server on the host / remote server / HPC system login node to the local client / Linux desktop / your notebook. This allows you to forward graphic interfaces and not only the terminal.
# Logging in with PuTTY
Launch `putty.exe` to log in. Under "_Category_", navigate to "_Session_" and set the _Host name (or IP address)_ for the system you want to connect to, e.g. `jureca.fz-juelich.de`.
This is not an error, but a security feature. Answer "Yes".
Contents:
[TOC]
# JURECA: Note on IPv6 connectivity
For users connecting from machines with a globally routed IPv6 address assigned to them, their SSH clients will favor IPv6. This can lead to issues for users who have uploaded SSH public keys with `from=` clauses based solely on IPv4 addresses or using patterns based on host names that do not match the host names their internet provider assigns to IPv6 addresses.
The long-term solution for these issues is to update your `from=` clauses to include patterns based on IPv6 addresses (or hostnames matching the IPv6 addresses).
**A short-term solution**: Revert to IPv4 connectivity.
1. Disallow IPv6 in your SSH client
- PuTTY: Set '_Internet protocol version_' in the '_Connection_' pane. See figure below.
- OpenSSH: Command line option `-4` or the configuration setting `AddressFamily inet` in `.ssh/config`
2. Connect to a new DNS name which will keep resolving to IPv4 addresses only: `jureca-ipv4.fz-juelich.de`.
The `-X` option in the ssh-command enables "X11 forwarding"; this allows you to forward the graphical output of the X graphics server on the host / remote server / HPC system login node to the local client / Linux desktop / your notebook. This allows you to forward graphic interfaces and not only the terminal.
# Logging in with PuTTY
Launch `putty.exe` to log in. Under "_Category_", navigate to "_Session_" and set the _Host name (or IP address)_ for the system you want to connect to, e.g. `jureca.fz-juelich.de`.
This is not an error, but a security feature. Answer "Yes".
The server key fingerprint displayed in the dialog has to be verified by comparing it to the known good fingerprint. JSC publishes SSH fingerprints for its systems through JuDoor. You can find them on the page you used to upload your public key.
