- This topic has 1 reply, 2 voices, and was last updated 1 hour, 3 minutes ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
Home › Forums › FABRIC Announcements › Bastion problems
Hi,
I have same problem with bastion. I created a new slice coupe minutes ago and I cannot ssh to the hosts. I am running ssh on Jupyter home or on my home machine. The result is same.
From Jupyter:
fabric@summer:SAGE-69%$ ssh -i /home/fabric/work/fabric_config/slice_key2 -F /home/fabric/work/fabric_config/ssh_config ubuntu@2001:610:2d0:fabc:f816:3eff:fe7a:13c7
Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
jiri_0000134222@bastion.fabric-testbed.net: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535
fabric@summer:SAGE-69%$ nslookup bastion.fabric-testbed.net
Server: 10.40.0.10
Address: 10.40.0.10#53
Non-authoritative answer:
Name: bastion.fabric-testbed.net
Address: 128.163.180.149
Name: bastion.fabric-testbed.net
Address: 141.142.140.10
Name: bastion.fabric-testbed.net
Address: 23.134.235.242
Name: bastion.fabric-testbed.net
Address: 152.54.15.12
Name: bastion.fabric-testbed.net
Address: 2620:0:c80:1000::43
Name: bastion.fabric-testbed.net
Address: 2600:2701:5000:a902::c
Name: bastion.fabric-testbed.net
Address: 2602:fcfb:3:ffff::2
— see how it looks like from my PC.
PS C:\Users\jiri> ssh -i fabric_config\slice_key2 -F fabric_config\ssh_config rocky@2001:400:a100:3090:f816:3eff:fe7b:bb30 Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
jiri_0000134222@bastion.fabric-testbed.net: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Connection closed by UNKNOWN port 65535
PS C:\Users\jiri> nslookup bastion.fabric-testbed.net
Server: ns.cesnet.cz
Address: 2001:718:1:1::2
Non-authoritative answer:
Name: bastion.fabric-testbed.net
Addresses: 2602:fcfb:3:ffff::2
2600:2701:5000:a902::c
2620:0:c80:1000::43
128.163.180.149
141.142.140.10
152.54.15.12
23.134.235.242
Hello Jiri,
The problem you show is different. Your attempt fails at authenticating to the bastion, which indicates you are using an incorrect bastion key. Others could not even connect to the bastion. PLease make sure you are using the right bastion key in your configuration.