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(a)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
--
If simple questions can be answered with a simple google query then why are there so many
of them?