as well, is 1.2.3.4 and 5.6.7.8 routable each to the other? If not, you'll have to ssh hop to get from 1.2.3.4 to 5.6.7.8.
--- Regards, Kevin Martin On Sat, Jul 15, 2017 at 8:18 PM, John Mellor <john.mel...@gmail.com> wrote: > On Sat, 2017-07-15 at 17:01 -0400, bruce wrote: > > Testing Digitalocean > > > > I can create a ssh key I can create a remote instance and poulate it > > with the key to be able to do > > > > ssh foo_user@1.2.3.4 > > > > and access the vm with no issue... > > > > however:: > > > > if i spin up 1.2.3.4, as well as 5.6.7.8 > > > > how can i be on box 1.2.3.4 and do ssh foo_user@5.6.7.8 > > > > if i'm spinning up 1.2.3.4 and 5.6.7.8 what do i need to provide in > > each box o accomplish this! > > First, the 5.6.7.8 machine is going to have to be running the ssh > daemon, and ssh is not blocked by the firewall or other means. I'm > assuming that its not a Windows machine or something else incapable of > supporting ssh. > > Next, this is not going to work if 5.6.7.8 is configured to use NAT > instead of bridge networking. Can you ping the machine? > > Finally, is sshd on 5.6.7.8 ancient, and configured to ignore > connections from 1.2.3.4, or is blocked from using the sshv2 protocol > or short keys? > > What does ssh -vvvv foo_user@5.6.7.8 return, and what does the sshd log > show on the target machine? If it does not show anything, you have > network issues, not ssh issues. > > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org >
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
