Operating system Tumbleweed; desktop KDE Plasma. I can ssh into my desktop machine from my phone (using JuiceSSH) using the local LAN address 192.168.178.48 When I try to ssh to my ISP static address, I get 'no route to host'. This also happens to a colleague trying to connect from another city (ie. from outside my LAN). I have moved my ssh port to a higher number, no longer 22. This is set in /etc/ssh/sshd_config and /etc/services. The port is forwarded to this machine in my router (Fritz!Box 7530). The higher port is opened in firewalld with protocol TCP. I get the same 'no route to host' if I disable the firewall. I am not convinced the port is really open to the world, although ssh within the LAN is working. Nmap scan report for aaa-bbb-ccc-ddd.dsl.in-addr.zen.co.uk (aaa.bbb.ccc.ddd) Host is up (0.0060s latency). Not shown: 995 filtered tcp ports (no-response) PORT STATE SERVICE 113/tcp closed ident 873/tcp open rsync 1080/tcp closed socks 5060/tcp open sip 8089/tcp open unknown When I visit https://www.whatsmyip.org/port-scanner/ and ask it to scan my ssh port number it times out, whereas for comparison it confirms 873 immediately. SSH from elsewhere into this machine used to work (running Leap, but I doubt that makes a difference). Have I forgotten a setting somewhere? Are there other tests to run? Bob -- Bob Williams No HTML please. Plain text preferred. https://useplaintext.email/