[EdLUG] Problem with ssh

[Colin Shorts]

Breadboard jumper wires will be your best friend - just make sure your
serial adapter is 3.3V or you might let the blue smoke out!

On Tue, 23 Jun 2020, 18:59 Alistair Boak, <alistairboak at gmail.com> wrote:

> Thank you Colin,
>
> I’ve looked at the board inside and its got a serial header and there are
> instructions on Google, however, the USB to serial cable that I have, the
> pins are 0.1” spacing and I need to find one with 0.075" or 0.05”, I’ll see
> what I can do over the coming week I have a micrometer and will check!
>
> Thanks again for getting back to me so soon.
>
> Cheers
>
> Alistair
>
> On 23 Jun 2020, at 18:49, Colin Shorts <colin.shorts at gmail.com> wrote:
>
> It might be worth trying a serial connection, looks to be fairly easy to
> solder on some headers and connect using a ttl USB adapter. The usual
> warnings apply - it's 3.3V, only connect ground, tx, and rx.
>
> Plenty of examples on Google 😁
>
> I've *never* done anything like that, honest!
>
> If you can't solder, now is a great time to pick up a very useful skill 😁
>
> -Colin
>
> On Tue, 23 Jun 2020, 18:12 Alistair Boak, <alistairboak at gmail.com> wrote:
>
>> Hi everyone,
>>
>> I’ve been playing with an old Seagate GoFlex Net that I have on my
>> internal network.
>>
>> I installed Archlinux/arm on a USB thumb drive, and it was working fine
>> until I had the brilliant idea (NOT) to see what would happen if I switched
>> the drive and used a live Ubuntu distro on it and tried to ssh into that!
>> (I’m wearing ear-muffs so I cant hear the laughter).
>>
>> Anyway, I can now no longer ssh into the original Archlinux/arm USB
>> drive, there is a reset button on the Seagate net which I had used on the
>> Archlinux/arm and it reset and continued working, however, it doesn’t do
>> anything since I plugged in the other drive.
>>
>> I can still see the Net it as I can ping it, and when I ssh I get a
>> ‘connection refused’ response.  I read some of the ssh man pages and it
>> said to try the debug option -v and -vv and -vvv and the output is shown
>> below:
>>
>> ssh: connect to host 192.168.1.179 port 22: Connection refused
>> bash-3.2# ssh -v alarm at 192.168.1.179
>> OpenSSH_7.8p1, LibreSSL 2.6.2
>> 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 *
>> 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# ssh -vv alarm at 192.168.1.179
>> OpenSSH_7.8p1, LibreSSL 2.6.2
>> 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 *
>> 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# ssh -vvv alarm at 192.168.1.179
>> OpenSSH_7.8p1, LibreSSL 2.6.2
>> 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 *
>> 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#
>>
>> Line 48 and 52 in /etc/ssh/ssh_config both have "Host *” written in them.
>>
>> Apologies for the very long email but any help would be gratefully
>> received - or do I just bin the device? (Joking)
>>
>> Cheers
>>
>> Alistair B
>> (One of several on this list)
>> --
>> EdLUG mailing list
>> EdLUG at lists.edlug.org.uk
>> https://lists.edlug.org.uk/mailman/listinfo/edlug
>
> --
> EdLUG mailing list
> EdLUG at lists.edlug.org.uk
> https://lists.edlug.org.uk/mailman/listinfo/edlug
>
>
> --
> EdLUG mailing list
> EdLUG at lists.edlug.org.uk
> https://lists.edlug.org.uk/mailman/listinfo/edlug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.edlug.org.uk/pipermail/edlug/attachments/20200623/0c69ad6a/attachment.html>