Everytime I upload the backup config on the first step the light glows a solid blue. After reboot it returns to a slow-blinking magenta and I cannot access dynalinks login.
Also, I cannot ssh to it as cmd will not let me type or paste the password - to which it eventually crashes. I don't quite understand the return to stock portion of the device page.
I should mention that i truly understand that it's not the backup config's fault and the error lies with the user or the device.
Quick update - I was able to access SSH by using onboard keyboard and typing in the password that way; though the console would not show the inputs and still took the entry. Anyone know of a fix for that?
File a bug with the people who provided the ssh client, they'll close it 1 sec after you've clicked save.
1 Like
Okay thank you, I made it to part two and can root into the router. It shows openWRT.
However, in a second cmd window I am trying to copy the factory file to the /tmp/ and am receiving a connection refused response.
Does this count as the image having failed as per -
"If you're unable to connect to 192.168.1.1, the initramfs boot failed"
I appreciate your fast reply!
Do you have multiple network connections going ?
If ssh works, so should scp.
1 Like
I did; right before you replied I was also routed into my fios gateway and assumed the ip's interfered with each other?
Not sure if that is correct but I am going to retry the following steps without the fios router involved and only using the dynalink. Thank you again frollic.
I am going to keep redundantly documenting in case someone else who is similarly new to this process goes through what I do.
After removing my isp router from the equation and only routing from my dynalink directly, I received an invalid path response. It turns out after swapping the routers around (which involved unplugging the dynalink) the dynalink reverted back to the old ip and I'm assuming default firmware. I will restart the process with this new setup.
@frollic
After resetting everything and making sure it is just the router itself I still get this no file/directory response
The missing file (or wrong name/folder) on your Windows box isn't an Openwrt issue.
1 Like
Ah so this is an OS issue then. I'll have to reinstall it, thank you.
Not what I meant, and you know it.
1 Like
I didn't actually know it, sorry for misunderstanding. A user issue then.
I assumed you meant an OS issues solely because I am using a lite/modded version of windows.
I believe your issue is that the default path for Windows command prompt is c:\windows\system32 -- and that it's very unlikely the path where you downloaded the Openwrt .ubi file.
Maybe change directory to the Downloads folder? 
Unrelated, but also, you may need the -O command line option with the SCP command. ( That is the case with Linux. )
2 Likes
I see, I didn't realize that was how the commands/terminal worked. Thank you for the suggestion! I am learning and thankful for the chance. Thank you to both you and frollic.
1 Like
I suggest you use winscp instead, then you can click around, and locate the file.
1 Like
I appreciate the idea frollic and thank you for being patient.
Okay after a few changes I have hit yet another snag so I apologize in advance.
After changing directory to match the file installation for the factory image I got a warning about a "man in the middle attack". It wasn't trusting the host it looked like.
After some research I used ssh-keygen -R (ip address). And it made it through, kind of.
It asked if I wanted to continue connecting to the host and then I was hit with:
ash: /usr/libexec/sftp-server: not found
scp: Connection closed
If anything shows up that I shouldn't be posting, please let me know. Again I am overdocumenting for someone as inexperienced as me in the future.
