1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • Still working on move to ssh

    From bcw142@21:1/145.3 to All on Wednesday, June 13, 2018 07:54:11
    Hit a snag. I see 'SSH-2.0-cryptlib' then after a while handshake failed and
    it stops from AlphaTest bcw142.zapto.org port 2322, took a look and that's right it's setup for ssh IPV4+IPV6 at port 2322. So what's SSH-2.0-cryptlib trying to tell me? I have the same version on both sides with same OS and setup so nodespy should work and does to Mystic Pi BBS port 22. So what's up with AlphaTest?
    mis.log of the event shows:
    + 2018.06.13 07:46:50 SSH 1-HostName sales.glaciercomputer.com
    + 2018.06.13 07:46:50 SSH 1-Negotiating SSH session
    + 2018.06.13 07:47:21 SSH 1-Session failed
    + 2018.06.13 07:47:35 SSH > Connect on slot 1/8 (::FFFF:ADA2:B1A1)
    + 2018.06.13 07:47:35 SSH 1-HostName sales.glaciercomputer.com
    + 2018.06.13 07:47:35 SSH 1-Negotiating SSH session
    + 2018.06.13 07:47:43 SSH 1-Session failed
    Never makes it to the node1.log because it didn't get connected. So I think this is the only log entry, seems like encryption failure of some type, but already have log level at 3 so what more is there to look for?

    This same setup works to Mystic Pi BBS ssh just fine (so not nodespy part). AlphaTest works to itself locally and via the net (bcw142.zapto.org). Recompiled and it made no difference (even after restarting mis) on remote
    end (AlphaTest seems to be working, it's 'Workpoint' that has issues).

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From bcw142@21:1/145 to bcw142 on Wednesday, June 13, 2018 09:06:38
    On 06/13/18, bcw142 said the following...

    Hit a snag. I see 'SSH-2.0-cryptlib' then after a while handshake failed and it stops from AlphaTest bcw142.zapto.org port 2322, took a look and that's right it's setup for ssh IPV4+IPV6 at port 2322. So what's SSH-2.0-cryptlib trying to tell me? I have the same version on both
    sides with same OS and setup so nodespy should work and does to Mystic
    Pi BBS port 22. So what's up with AlphaTest?

    Found it! Protocol had moved back to TELNET from SSH, put it back and it's connecting fine. So if you see 'SSH-2.0-cryptlib' then after a while
    handshake failed check the Protocol line of the Phonebook if using nodespy.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)