On 9/18/19 5:05 AM, Garry T. Williams wrote:
On Saturday, September 14, 2019 10:13:11 AM EDT Ed Greshko wrote:
On 9/14/19 9:59 PM, Patrick Dupre wrote:
On 9/14/19 9:34 PM, Patrick Dupre wrote:
telnet 192.168.1.12
Trying 192.168.1.12...
telnet: connect to address 192.168.1.12: No route to host
I guess that I need to reestablish the route.
How?
No, that is an indication that port 22 is not open.
No. That error is from an ICMP message and means exactly what it
says. It has nothing to do with what is or is not listening on the
remote host since the attempt to connect to 192.168.1.12 never got
that far.
You do not have a route to 192.168.1.12 from the host that you
used to run the telnet command.
Why don't you test before you comment?
I use keys for authentication so no passwords are needed.
Login to remote host
[egreshko@meimei ~]$ ssh 192.168.1.55
Last login: Wed Sep 18 05:28:17 2019 from 192.168.1.18
[egreshko@f31bk ~]$
Close the ssh port
[egreshko@f31bk ~]$ sudo firewall-cmd --remove-service=ssh
[sudo] password for egreshko:
success
Exit
[egreshko@f31bk ~]$ exit
logout
Connection to 192.168.1.55 closed.
Reconnect to the remote host
[egreshko@meimei ~]$ ssh 192.168.1.55
ssh: connect to host 192.168.1.55 port 22: No route to host
Look at that......
--
If simple questions can be answered with a simple google query then why are
there so many of them?
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
