Forum Replies Created
-
Posts
-
The second workaround you mentioned is just a command line representation of the jump instructions in the ~/work/.ssh/config file.
the -F is required when using jupyterHub because ssh looks for its config file in ~/.ssh/config . When using JupyterHub, this is not possible for persistence since the files in ~/ gets reset. Instead the docs talk about saving files that need to be persistent in ~/work. Hence the ssh config directory is stored in ~/work/.ssh/config and thus the need for the -F to tell ssh where the config file resides .
If you VM is using an IPv6 address, which is the case with all FABRIC sites except MAX, then sites like github and dockerhub may not be accessible wince they are IPv4 only. A temporary solution is to use a NAT64 as mentioned on https://nat64.net/
The IPs you are trying are not your VMs. Those were examples mentioned in the documentation. You should replace those with the IPs you obtain after creating your VMs
Here is my version of the ssh config file. Its advisable to save it in ~/work/.ssh/config rather than ~/.ssh/config since ~/work is persistent upon re-creation of the jupyterhub instance
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
ServerAliveInterval 120Host bastion-?.fabric-testbed.net
User <your bastion host username>
ForwardAgent yes
Hostname %h
IdentityFile <path to your bastion host private key>
IdentitiesOnly yesHost * !bastion-?.fabric-testbed.net
ProxyJump <your bastion host username>@bastion-1.fabric-testbed.net:22
##ProxyJump <your bastion host username>@bastion-2.fabric-testbed.net:22Once this file is saved, you no longer need the -J param as long as this file is included in your ssh command .
For example.
ssh -F ~/work/.ssh/config centos@63.239.135.94 should work
