Hello,
ssh does not respond (time out, the machine is OK). Hence, I restarted it and
systemctl status sshd ● sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset> Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago Docs: man:sshd(8) man:sshd_config(5) Main PID: 29012 (sshd) Tasks: 1 (limit: 4915) Memory: 1.0M CGroup: /system.slice/sshd.service └─29012 /usr/sbin/sshd -D -oCiphers=aes256-gcm@openssh.com,chacha20->
Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon... Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22. Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22. Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.
But it is not enough. What else should I do?
Thank.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 ===========================================================================
On 9/14/19 9:34 PM, Patrick Dupre wrote:
Hello,
ssh does not respond (time out, the machine is OK). Hence, I restarted it and
systemctl status sshd ● sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset> Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago Docs: man:sshd(8) man:sshd_config(5) Main PID: 29012 (sshd) Tasks: 1 (limit: 4915) Memory: 1.0M CGroup: /system.slice/sshd.service └─29012 /usr/sbin/sshd -D -oCiphers=aes256-gcm@openssh.com,chacha20->
Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon... Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22. Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22. Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.
But it is not enough. What else should I do?
I assume you mean that when you attempt to ssh to the machine from a remote system it times out?
First Q is, did you make sure port 22 is opened on the server?
From the remote system, what do you get when you try to "telnet" to port 22?
It should be simiiar to this
[egreshko@meimei ~]$ telnet 192.168.1.55 22 Trying 192.168.1.55... Connected to 192.168.1.55. Escape character is '^]'. SSH-2.0-OpenSSH_8.0 ^] telnet> close Connection closed.
On 9/14/19 9:34 PM, Patrick Dupre wrote:
Hello,
ssh does not respond (time out, the machine is OK). Hence, I restarted it and
systemctl status sshd ● sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset> Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago Docs: man:sshd(8) man:sshd_config(5) Main PID: 29012 (sshd) Tasks: 1 (limit: 4915) Memory: 1.0M CGroup: /system.slice/sshd.service └─29012 /usr/sbin/sshd -D -oCiphers=aes256-gcm@openssh.com,chacha20->
Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon... Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22. Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22. Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.
But it is not enough. What else should I do?
I assume you mean that when you attempt to ssh to the machine from a remote system it times out?
First Q is, did you make sure port 22 is opened on the server?
I guess, from the machine itself (192.168.1.12), the ssh works OK
From the remote system, what do you get when you try to "telnet" to port 22?
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?
It should be simiiar to this
[egreshko@meimei ~]$ telnet 192.168.1.55 22 Trying 192.168.1.55... Connected to 192.168.1.55. Escape character is '^]'. SSH-2.0-OpenSSH_8.0 ^] telnet> close Connection closed.
-- 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-leave@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
On 9/14/19 9:59 PM, Patrick Dupre wrote:
On 9/14/19 9:34 PM, Patrick Dupre wrote:
Hello,
ssh does not respond (time out, the machine is OK). Hence, I restarted it and
systemctl status sshd ● sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset> Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago Docs: man:sshd(8) man:sshd_config(5) Main PID: 29012 (sshd) Tasks: 1 (limit: 4915) Memory: 1.0M CGroup: /system.slice/sshd.service └─29012 /usr/sbin/sshd -D -oCiphers=aes256-gcm@openssh.com,chacha20->
Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon... Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22. Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22. Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.
But it is not enough. What else should I do?
I assume you mean that when you attempt to ssh to the machine from a remote system it times out?
First Q is, did you make sure port 22 is opened on the server?
I guess, from the machine itself (192.168.1.12), the ssh works OK
That doesn't tell you anything. The firewall doesn't block connections on the server to the server.
From the remote system, what do you get when you try to "telnet" to port 22?
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.
On the server you should see ssh included like so in this command
[root@f31bk ~]# firewall-cmd --permanent --list-services dhcpv6-client mdns ssh
If not listed, you can then do
firewall-cmd --permanent --add-service=ssh
On 9/14/19 10:13 PM, Ed Greshko wrote:
On 9/14/19 9:59 PM, Patrick Dupre wrote:
On 9/14/19 9:34 PM, Patrick Dupre wrote:
Hello,
ssh does not respond (time out, the machine is OK). Hence, I restarted it and
systemctl status sshd ● sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset> Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago Docs: man:sshd(8) man:sshd_config(5) Main PID: 29012 (sshd) Tasks: 1 (limit: 4915) Memory: 1.0M CGroup: /system.slice/sshd.service └─29012 /usr/sbin/sshd -D -oCiphers=aes256-gcm@openssh.com,chacha20->
Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon... Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22. Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22. Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.
But it is not enough. What else should I do?
I assume you mean that when you attempt to ssh to the machine from a remote system it times out?
First Q is, did you make sure port 22 is opened on the server?
I guess, from the machine itself (192.168.1.12), the ssh works OK
That doesn't tell you anything. The firewall doesn't block connections on the server to the server.
From the remote system, what do you get when you try to "telnet" to port 22?
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.
On the server you should see ssh included like so in this command
[root@f31bk ~]# firewall-cmd --permanent --list-services dhcpv6-client mdns ssh
If not listed, you can then do
firewall-cmd --permanent --add-service=ssh
Oh, you may also have to do "firewall-cmd --add-service=ssh"
for immediate effect.
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.
Not necessarily. You can certainly get "No route to host", rather than "Connection failed" if the port is not open.
On September 17, 2019 9:05:34 PM UTC, "Garry T. Williams" gtwilliams@gmail.com 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.
-- Garry T. Williams
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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
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......
-
Ed Greshko -
Garry T. Williams -
John M. Harris, Jr. -
Patrick Dupre