Results 1 to 8 of 8

Thread: Unable to ssh into computer

  1. #1

    Default Unable to ssh into computer

    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:

    Code:
    :~> 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. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,012
    Blog Entries
    3

    Default Re: Unable to ssh into computer

    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.
    openSUSE Leap 15.1; KDE Plasma 5;

  3. #3

    Default Re: Unable to ssh into computer

    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. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,605

    Default Re: Unable to ssh into computer

    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
    Code:
    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).
    Henk van Velden

  5. #5

    Default Re: Unable to ssh into computer

    `htop` is a fancier version of `top`

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

  6. #6
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,478
    Blog Entries
    14

    Default Re: Unable to ssh into computer

    Quote Originally Posted by riabovvv View Post
    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`
    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.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  7. #7

    Default Re: Unable to ssh into computer

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

  8. #8
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,605

    Default Re: Unable to ssh into computer

    Quote Originally Posted by riabovvv View Post
    `htop` is a fancier version of `top`
    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.
    Henk van Velden

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •