[EdLUG] Problem with ssh

[Justin B Rye]

Alistair Boak wrote:
> I’ve been playing with an old Seagate GoFlex Net that I have on my
> internal network.
[...]
> bash-3.2# ssh -vvv alarm at 192.168.1.179
> OpenSSH_7.8p1, LibreSSL 2.6.2

A noughties shell version number combined with modern network
software?  Weird, but better than the reverse.

> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 48: Applying options for *
> debug1: /etc/ssh/ssh_config line 52: Applying options for *

(Whatever options you're defining for "any host", you probably don't
need to say it twice, but that's sure to be a red herring.)

> debug2: resolve_canonicalize: hostname 192.168.1.179 is address
> debug2: ssh_connect_direct
> debug1: Connecting to 192.168.1.179 [192.168.1.179] port 22.
> debug1: connect to address 192.168.1.179 port 22: Connection refused
> ssh: connect to host 192.168.1.179 port 22: Connection refused
> bash-3.2# 

Before you break out the soldering iron, there are a couple of things
you can do to check whether you're really reaching an SSH server and
being blocked there or whether this is a misleading error message.  If
you probe it with something like netcat, do you see a plausible reply?
Come to think of it, never mind fancy network diagnostics, just say:

 $ cat < /dev/tcp/192.168.1.179/22

and you should get at least an SSH banner back...
-- 
Justin B Rye
http://jbr.me.uk/