Search results

Agreed and I did that. I sent a message to the bug submit process but never heard back. I uninstalled and removed all of the registry entries but no change. Its exactly the same on 2 different laptops in terms of the behavior and the versions. Its not a major issue for me now because once my...

It turns out the issue is with putty v0.82 connecting to my Asus, which is running an older version of dropbear. I do not know what in putty is causing it to fail but v0.81 works fine from everywhere and v0.82 fails from everywhere.

Well I guess this thread died on the vine lol.

Here are the screenshots from putty that you requested. Here is the result of the plink command that you asked about, after saving the profile with the keepalive settings. Looking up host "192.168.x.x" for SSH connection Connecting to 192.168.x.x port 22 We claim version...

I am only using plink as requested from @Martinski to see the output. I do not normally use plink but in my experience using it for this thread, it does connect in an interactive session. When I issue the connect command, it prompts me for password and I get to an interactive session where I...

I think the only thing I did not provide was the output from the failed plink v0.82. I thought the point was to show the successful output so I posted all of that. Here is the output from the plink v0.82 error: Looking up host "192.168.x.x" for SSH connection Connecting to 192.168.x.x port 22...

I checked and both of those options are set that way in the profile.

Does this ring any bells?

Thanks. I am using name/password with SSH to connect to my AC68U so if I am readin it correctly, using the plink command you mentioned won't work because I am not using a key file to authenticate. So I used the "-l" option to specify password instead. When us9ng the v0.82 version of plink, I...

Looking around on the asus, I have found there's a ".ssh" directory that has 2 files, authorizedkeys and known_hosts. I can view the known_hosts and it has 1 line with my IP and ssh key. The authorizedkeys appears empty or I just can't open it because when I run "cat" on it, it shows nothing...

Yeah it looks like the SSH on the router does not have the "-Q" parameter. I have been trying to scan files to see if its in a config file or something but so far no luck. Is there any other way to find the available kex? I was not aware of the RND file so IDK if that was deleted or not. I...

I am in an SSH session with the Asus and those commands do not work. SSH is there but the arguments you have do not work. I am guessing its the version of ssh thats installed in the RMerlin build.

My Asus is sitting behind my ISP modem/router so I am running in double-NAT. That's how its always been. I have not intentionally let it get old but I do not touch it on a constant basis and when the update path is to reset to bare metal, I hate taking the time to do the whole process. I have...

I am running v384.19. Yes, I know its old. LOL I have removed the save entry many times and tried so many different ways and it fails immediately. As soon as I use putty 0.81 or any other SSH client, it works fine.

I would but I intend to replace this thing soon. It is SOOOO old. It has been great for a long time. I have fallen behind so many times and had to reflash and start over, which I hate doing, so I am trying something else soon. For right now, I need to keep this running until I get the new...

Not sure how to do that. Here is a shot of both putty versions with the Kex options and they look identical. I also ran the command you sent and the closest line I found to what you posted was "debug1: kex: algorithm: curve25519-sha256". That was run from the ssh command on my laptop...

Ok, I think I found it. My "working" laptop is using putty 0.81. My "non-working" laptop is 0.82. I tried the exe for 0.81 on the "non-working" laptop and it connected. So for some reason, putty 0.82 will not connect to my AsusWRT running RMerlin. Now my router is running a quite old...

Yes, I have reinstalled 0.82 several times and also tried the dev version. The same version works on my other laptop and used to work on this one.

My last posts show the data since I found it in SSH. Dec 4 13:48:06 dropbear[14732]: Child connection from 192.168.x.x:53823 Dec 4 13:48:06 dropbear[14732]: Exit before auth from <192.168.x.x:53823>: No matching algo kex

OK I looked in the syslog.log file right after I tried to connect. Here is what I found: Dec 4 13:48:06 dropbear[14732]: Child connection from 192.168.x.x:53823 Dec 4 13:48:06 dropbear[14732]: Exit before auth from <192.168.x.x:53823>: No matching algo kex Any ideas on what this could be...