• SSH in Win 10 / 64 (a38)

    From Ktulu@21:2/122 to All on Tue Apr 10 13:06:40 2018
    Hi all,

    I have recently tried setting up my SSH server in Win 10 64-bit. I have cryptlib .DLL (cl64.dll) (mentioned in the wiki) in my mystic folder, forwarded the port on my router, have the VC Runtime installed, but when i try to
    connect to that port, it connects and then aborts the connection right away.
    Is there something i have missed? Do I need to register the DLL or something?

    Thanks!

    |08---
    |07-|12Ktulu
    |15SysOp @ |12Insane Asylum |07BBS
    |07telnet://bbs.asylumbbs.net port 28

    --- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
    * Origin: Insane Asylum (21:2/122)
  • From shinobi@21:1/153 to Ktulu on Tue Apr 10 18:57:02 2018
    I have recently tried setting up my SSH server in Win 10 64-bit. I have cryptlib .DLL (cl64.dll) (mentioned in the wiki) in my mystic folder, forwarded the port on my router, have the VC Runtime installed, but when
    i try to connect to that port, it connects and then aborts the
    connection right away. Is there something i have missed? Do I need to register the DLL or something?

    Tye to put it in Your PATH.

    Regards

    Shinobi

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
    * Origin: INFOLINKA BBS (21:1/153)
  • From g00r00@21:1/108 to Ktulu on Tue Apr 10 16:12:38 2018
    Hi all,

    I have recently tried setting up my SSH server in Win 10 64-bit. I have cryptlib .DLL (cl64.dll) (mentioned in the wiki) in my mystic folder, forwarded the port on my router, have the VC Runtime installed, but when
    i try to connect to that port, it connects and then aborts the
    connection right away. Is there something i have missed? Do I need to register the DLL or something?

    The server won't even start up if the .DLL is missing, so it sounds like its not the .DLL itself.

    Did you look in the mis.log/node logs to see if there is an error?

    You could also try to stop the server, delete "ssl.cert" in your DATA folder, and restart.

    What terminal are you using to connect?

    It could also be a bug as many socket changes are happening.

    --- Mystic BBS v1.12 A39 2018/04/08 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Pequito@21:1/126 to Ktulu on Tue Apr 10 14:33:46 2018
    On 04/10/18, Ktulu said the following...

    Hi all,

    I have recently tried setting up my SSH server in Win 10 64-bit. I have cryptlib .DLL (cl64.dll) (mentioned in the wiki) in my mystic folder, forwarded the port on my router, have the VC Runtime installed, but when
    i try to connect to that port, it connects and then aborts the
    connection right away. Is there something i have missed? Do I need to register the DLL or something?


    When you load mystic server does it show it bind the port with no errors?

    Cheers!
    Pequito

    --- Mystic BBS v1.12 A39 2018/04/10 (Linux/64)
    * Origin: Twinkle BBS # (21:1/126)
  • From Ktulu@21:2/122 to Pequito on Wed Apr 11 00:49:08 2018
    When you load mystic server does it show it bind the port with no errors?

    Cheers!
    Pequito

    No errors at all.

    As I stated, have the cl64.dll in my mystic folder gonna move it to
    somewhere else within my path, and see if it helps.

    I'll post my progress.

    |08---
    |07-|12Ktulu
    |15SysOp @ |12Insane Asylum |07BBS
    |07telnet://bbs.asylumbbs.net port 28

    --- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
    * Origin: Insane Asylum (21:2/122)
  • From g00r00@21:1/108 to Ktulu on Wed Apr 11 13:35:36 2018
    No errors at all.

    As I stated, have the cl64.dll in my mystic folder gonna move it to somewhere else within my path, and see if it helps.

    I'll post my progress.

    You might want to try the latest A39 prealpha if you're having problems with SSH in A38. The code is so different in A39 that its not even worth investigating any socket issues from A38.

    As you probably know since A35 there have been major major changes to server and socket code, and with that it takes some time to work out the kinks. A39 should be more stable by far in those areas, even in prealpha form.

    Not only am I getting close to a full A39, but we're also getting close to a full 1.12 release.

    --- Mystic BBS v1.12 A39 2018/04/11 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Pequito@21:1/126 to g00r00 on Wed Apr 11 15:37:56 2018
    On 04/11/18, g00r00 said the following...

    You might want to try the latest A39 prealpha if you're having problems with SSH in A38. The code is so different in A39 that its not even worth investigating any socket issues from A38.

    With that being said would this affect Rlogin using IR, I had/have a
    DoorParty connection using RLogin which no longer connects in A39 but did in A38. Telnet seems to be working OK have not seen any issues there.

    Cheers!
    Pequito

    --- Mystic BBS v1.12 A39 2018/04/10 (Linux/64)
    * Origin: Twinkle BBS # (21:1/126)
  • From g00r00@21:1/108 to Pequito on Wed Apr 11 20:20:12 2018
    With that being said would this affect Rlogin using IR, I had/have a DoorParty connection using RLogin which no longer connects in A39 but
    did in A38. Telnet seems to be working OK have not seen any issues
    there.

    Upgrade to the latest version...

    --- Mystic BBS v1.12 A39 2018/04/11 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Ktulu@21:2/122 to g00r00 on Thu Apr 12 01:15:02 2018
    That's a lot of good news right there. I did quite a bit of testing on Pequito's a39 system, like dropping carrier while in a door, dropping carrier while the bbs is 'thinking' (performing a disk task) IT worked flawlessly and there was no sign of any type of node ghosting.

    Yeah I will have to just upgrade to A39.

    Have you done any type of stress testing such as setting up 100 nodes on
    mystic and getting 100 connections? or anything similar? I'd love to see the results of that, I think you've done a great job with mystic this far, and
    look forward to the future features of Mystic.

    I haven't gotten a chance ot play any further with the SSH server, But maybe I will just continue that once I get a39 installed.

    Thanks for the reply!



    You might want to try the latest A39 prealpha if you're having problems with SSH in A38. The code is so different in A39 that its not even worth investigating any socket issues from A38.

    As you probably know since A35 there have been major major changes to server and socket code, and with that it takes some time to work out the kinks. A39 should be more stable by far in those areas, even in
    prealpha form.

    Not only am I getting close to a full A39, but we're also getting close
    to a full 1.12 release.


    |08---
    |07-|12Ktulu
    |15SysOp @ |12Insane Asylum |07BBS
    |07telnet://bbs.asylumbbs.net port 28

    --- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
    * Origin: Insane Asylum (21:2/122)
  • From Pequito@21:1/126 to g00r00 on Thu Apr 12 04:51:36 2018
    On 04/11/18, g00r00 said the following...

    With that being said would this affect Rlogin using IR, I had/have a DoorParty connection using RLogin which no longer connects in A39 but did in A38. Telnet seems to be working OK have not seen any issues there.

    Upgrade to the latest version...

    Did per the other thread and is working again. :)

    Cheers!
    Pequito

    --- Mystic BBS v1.12 A39 2018/04/11 (Linux/64)
    * Origin: Twinkle BBS # (21:1/126)
  • From g00r00@21:1/108 to Ktulu on Thu Apr 12 14:43:48 2018
    Have you done any type of stress testing such as setting up 100 nodes on mystic and getting 100 connections? or anything similar? I'd love to see the results of that, I think you've done a great job with mystic this
    far, and look forward to the future features of Mystic.

    Yes I do often. This morning actually I did one in Linux with the Telnet server after removing some experimental code that I accidentally left in the last couple prealpha builds. It had 30+ nodes active at once, zero crashes, zero ghost nodes, and MIS never went above 3% CPU. UI was responsive. It was a shorter test though only ~20,000 connections total. I've done up to around 250,000 in the past.

    (This is with the next pre-alpha build of A39 (probably released tonight at midnight 4/13). It should be the last prealpha build before A39).

    On the Windows side I hit the HTTP server using Apache jMeter load testing with 50 concurrent browsing users. No crashes.

    I want to develop software to load test the BINKP server I just haven't gotten around to it yet but there may still be an issue there that can cause some crashing. Avon has shown he's had 16-20 simultaneous BINKP connections going in the past, but he has also reported some crashes here and there too.... But that might have been the experimental code I just realized was left in.

    --- Mystic BBS v1.12 A39 2018/04/11 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Ktulu@21:2/122 to g00r00 on Fri Apr 13 00:43:42 2018
    Wow! That IS good news! Sounds to me like you've put it to the test. I think at the rate you're doing pre-alphas, I'm just gonna wait until it's released. LOL!

    Do you have any near future plans to upgrade from using python 2.7 to version 3 to enable the ability to start using threads? I think with projects such as what Gryphon has, threading would come in handy for his irc client project.

    Also, are there any future plans to further MPL in any way, such as exposing socket type functions for making servers or anything of that sort?

    A month or so ago, you mentioned you were getting burnt out, and I can understand why at times, when you spend all night working on seomthing and
    you think it's bulletproof and then someone comes along and says it's not working. Sounds to me like you've got your energy back. I know that Real life stuff gets in the way once in awhile.




    Yes I do often. This morning actually I did one in Linux with the Telnet server after removing some experimental code that I accidentally left in the last couple prealpha builds. It had 30+ nodes active at once, zero crashes, zero ghost nodes, and MIS never went above 3% CPU. UI was responsive. It was a shorter test though only ~20,000 connections
    total. I've done up to around 250,000 in the past.
    (This is with the next pre-alpha build of A39 (probably released tonight at midnight 4/13). It should be the last prealpha build before A39).
    On the Windows side I hit the HTTP server using Apache jMeter load
    testing with 50 concurrent browsing users. No crashes.
    I want to develop software to load test the BINKP server I just haven't gotten around to it yet but there may still be an issue there that can cause some crashing. Avon has shown he's had 16-20 simultaneous BINKP connections going in the past, but he has also reported some crashes
    here and there too.... But that might have been the experimental code I just realized was left in.

    |08---
    |07-|12Ktulu
    |15SysOp @ |12Insane Asylum |07BBS
    |07telnet://bbs.asylumbbs.net port 28

    --- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
    * Origin: Insane Asylum (21:2/122)
  • From g00r00@21:1/108 to Ktulu on Fri Apr 13 12:18:44 2018
    Wow! That IS good news! Sounds to me like you've put it to the test.
    I think at the rate you're doing pre-alphas, I'm just gonna wait until it's released. LOL!

    Yep at this point if you haven't upgraded from A38 you might as well wait since it'll probably be in the next week.

    Wow! That IS good news! Sounds to me like you've put it to the test.
    I think at the rate you're doing pre-alphas, I'm just gonna wait until it's released. LOL!

    I ended up doing 1.8 million connections 200 simultaneous users on the HTTP server yesterday no issues.

    Do you have any near future plans to upgrade from using python 2.7 to version 3 to enable the ability to start using threads? I think with

    No. Python 3 is not really an upgrade to Python 2 they are incompatible languages (the code is not compatible). The majority of the major libraries people want to use are for Python 2, few use Python 3 in the professional world (I've never seen it even once as a consultant), etc. Python 2 is the default for OSX, most Linux distributions, etc. Python 2 supports threads you don't need 3 for that.

    Also, are there any future plans to further MPL in any way, such as exposing socket type functions for making servers or anything of that sort?

    I add MPL stuff here and there, but I don't have plans at the moment for socket stuff.

    A month or so ago, you mentioned you were getting burnt out, and I can understand why at times, when you spend all night working on seomthing

    I did? I don't remember saying I was burned out on Mystic.

    --- Mystic BBS v1.12 A39 2018/04/12 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)