Unable to ssh into computer

English Network/Internet
1

I have a LEAP 15 machine with sshd up and running. No custom setup for sshd were ever made. Firewall is disabled. I try to connect to this machine over ssh and get a timed out error:

:~> ssh -v username@192.168.31.12
OpenSSH_7.6p1, OpenSSL 1.1.0i-fips  14 Aug 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 25: Applying options for *
debug1: Connecting to 192.168.31.12 [192.168.31.12] port 22.
debug1: connect to address 192.168.31.12 port 22: Connection timed out
ssh: connect to host 192.168.31.12 port 22: Connection timed out

I can ping this machine.

2

Recheck whether the firewall is really disabled on the machine you are connecting to. That looks like a firewall problem to me.

Keep in mind that the firewall is changed for Leap 15. It is now “firewalld” rather than the old SuSEfirewall2. So “systemctl” commands that you used in earlier openSUSE release might not be correct for Leap 15.0.

3

Recheck whether the firewall is really disabled on the machine you are connecting to

I don’t see firewalld in htop, yast service manager indicates that firewalld is down, yast firewall configuration when launches tells me that it can’t connect to the firewalld.

This system is an upgrade from 42.2 so I checked if older version somehow survived and working but htop doesn’t filter service like SuSEfirewall2

4

I do not know exactly what htop is (I seem not to have it on my system), but when I wanted to know if a process called firewald is running, I would do

ps -ef | grep firewalld

or similar.

As there was no gracefull uograde from SuSEfirewall2 to firewalld, you must do something yourself (as the Relaese documention mention IIAC).

5

htop is a fancier version of top

:~> ps -ef | grep firewalld
master    6534  5869  0 20:01 pts/4    00:00:00 grep --color=auto **firewalld**
6

Remove SuSEfirewall2, and replace it by firewalld. You now have a situation where the YaST module is looking for the firewalld instance, where you have the old SuSEfirewall2 still active.

7

After removing SuSEfirewall2 I was able to login via ssh, thanks:)

8

I guessed that, but as top is used to find heavy system using processes and not to find a process by name (what was what you intended probably), I doubted what it should do.

In any case, you did the switch to firewalld now and that is fine.