search

AnttiTakala / SSH2DOS

Fork of SSH2DOS with more up to date cipher and SHA256 support
GNU General Public License v2.0
59 stars 6 forks source link

PC hangs when running ssh2dos in TCP/IP setup #1

Open velouria opened 3 years ago

velouria commented 3 years ago

Packet driver was correctly configured: 3Com Etherlink III with 3C509.exe. mTCP DHCP got an IP lease and could reach network. PC hangs when running ssh2dos in TCP/IP setup. Tried with old ssh2dos (v0.2.1) and it does the TPC/IP setup but fails connecting due to old protocols being used.

AnttiTakala commented 3 years ago

Which CPU does your system have? I have only tested the programs with a Pentium as I don't currently have anything older. I suspect there might be something misconfigured in my watt32 compilation.

I'll try to test with PCem.

velouria commented 3 years ago

Which CPU does your system have? I have only tested the programs with a Pentium as I don't currently have anything older. I suspect there might be something misconfigured in my watt32 compilation.

I'll try to test with PCem.

It's 486 DX4. If I can provide any logs pls let me know how to do it (I tried logging the session but it doesn't log anything before it halts).

AnttiTakala commented 3 years ago

Ok! I actually do have a DX2/DX4 system I can try with and also a 3C509.

Did you run only with ssh2dos.exe or also with ssh2d386.exe? emm386 or similar loaded? How much free memory?

How long did you wait? If the program actually starts generating the key, it might take a long time to finish.

velouria commented 3 years ago

Update: ssh2d386 seems to work fine. Thanks for the tip! After running ssh2d386 and being able to connect to the other host, I tried again with ssh2dos and it worked... But if I run ssh2dos first, after a reboot, it still halts the PC... 🤔

AnttiTakala commented 3 years ago

Great to hear!

Sounds like a bug in the non-386 version that needs investigation. On the other hand they are so slow that they might be useless in most cases anyway.

velouria commented 3 years ago

Thanks! Actually the behavior is a bit random. I'm able to connect but on the next try I get "No ARP reply". It seems like I need to connect to the host with ssh2d386 and only after that I can run other commands (scp2d386 for instance)... I know it doesn't make much sense but that's what I'm experiencing. :( In any case it works and I was able to transfer files between my old 486 PC and a Mac.